Skip to content

Fix flaky image build #4

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

Closed
psftw opened this issue Nov 5, 2019 · 3 comments
Closed

Fix flaky image build #4

psftw opened this issue Nov 5, 2019 · 3 comments

Comments

@psftw
Copy link
Contributor

psftw commented Nov 5, 2019

Note: the original GitHub repository was deleted recently, so we've lost all the issues/discussion 😢

Building this image is difficult due to issues with GnuPG and key servers. More details in https://github.com/docker-library/faq#openpgp--gnupg-keys-and-verification

The most straight-forward solution would be to directly embed the keys in this repository, though this is not ideal.

@phadej
Copy link
Contributor

phadej commented Nov 7, 2019

As far as I see, the gpg checks are used only for stack, would a solution to embed the sha512 sum into Dockerfiles instead?

It's a bit more work to update stack versions, but maybe better than flaky builds?

@psftw
Copy link
Contributor Author

psftw commented Nov 20, 2019

We have signed artifacts and keys so we might as well use them as intended vs checksums. It turns out, embedding the keys adds more complexity than I'm OK with ( psftw@465e064 ). Splitting up the single RUN command similarly without embedding keys would also help with flakiness, which seems like the right approach.

@psftw
Copy link
Contributor Author

psftw commented Feb 21, 2020

pushed up changes which split up the build to make fail faster which is the best we can do for now

@psftw psftw closed this as completed Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants