You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thank you very much for this project. It looks quite promising.
I want to use nix2container to automate building of container images, and doing that on my CI requires to be executed within a container image. What better way than to build that container image with nix2container?
However, that just added a bunch of stuff, but it still built those derivations. I guess it is due to the drv files not being copied, but just the resulting outpath?
Is there a way to add "nix cache" to the image itself?
PS. I'm also using the nixpkgs nix-flakes docker image as base as it seemed quite difficult to get a working nix image otherwise. First it complained about build users not working and when I got that working it refused to build the same image I built within that image, seems those derivations were "locked" and caused issues.
The text was updated successfully, but these errors were encountered:
Hello, thank you very much for this project. It looks quite promising.
I want to use
nix2container
to automate building of container images, and doing that on my CI requires to be executed within a container image. What better way than to build that container image withnix2container
?Currently I have this:
This is working, but then the image has to build (or pull from cache I guess, haven't enabled yet):
/nix/store/y7pja4n2b04j45sknwmivkl27mg3dgg1-skopeo-1.14.2.drv
/nix/store/p387dfxsh9myf2bc6lbdpngp8idilvrg-nix2container-1.0.0-go-modules.drv
/nix/store/699r95xr9zxdd013z06h7i3y954li8w0-nix2container-1.0.0.drv
But I wanted these derivations to be part of the image, I thought I could achieve this with:
However, that just added a bunch of stuff, but it still built those derivations. I guess it is due to the drv files not being copied, but just the resulting outpath?
Is there a way to add "nix cache" to the image itself?
PS. I'm also using the nixpkgs nix-flakes docker image as base as it seemed quite difficult to get a working nix image otherwise. First it complained about build users not working and when I got that working it refused to build the same image I built within that image, seems those derivations were "locked" and caused issues.
The text was updated successfully, but these errors were encountered: