New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dockerTools: use skopeo on the right platform #63865
dockerTools: use skopeo on the right platform #63865
Conversation
Lets just get rid of the |
@arianvp Good point. I am going to try out, and maybe also fix, the |
7ee5b60
to
942becc
Compare
@arianvp |
Great. LGTM! |
@GrahamcOfBorg test docker-tools |
@GrahamcOfBorg test docker-tools There seemed to have been some kind of transient failure |
Alas, the error doesn't seem to be transient on |
@arianvp I notice that on |
@arianvp This is the reason for that error: 4a4561c#diff-f5fad34a5e280fe300df690ac61dc673R122 It is deleting the VM drive before |
74594a6
to
fbd040e
Compare
fbd040e
to
ceab72e
Compare
@GrahamcOfBorg test docker-tools |
I think I just spawned a test seconds before you force-pushed. So it might fail again haha |
@GrahamcOfBorg test docker-tools |
Hmm, the test seems to time out on x86_64 whilst |
@arianvp I tried the I want to try running these tests locally. How can I run this specific test? |
|
@arianvp Work fine here. I cannot reproduce the timeout. See the gist: |
@dingxiangfei2009 the reason is that not all build machines support nested kvm, so they emulate x86 and are slow. so this is why it's failing. Not because there is something wrong with the test. Lets get this merged |
This looks correct to me and I don't think there should be a reason to suspect that it should be slower on Hydra than the current release-blocker docker test. Let's keep an eye on it regardless. :) |
Motivation for this change
When building a Docker image using any one of the
dockerTools
inpkgsCross
, askopeo
on the host platform is chosen and usually this leads to unrecognised Exec format. This PR fixes this issue by assigning the right build packages on the build platform.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)