Dockerfile: Remove mirror site setting; it broke the build#3874
Open
0cjs wants to merge 1 commit into
Open
Conversation
The ubuntu.cs.utah.edu mirror appears to be obsolete; trying to use it
produces error messages along the lines of:
Ign:2 https://ubuntu.cs.utah.edu/ubuntu jammy-updates InRelease
Err:2 https://ubuntu.cs.utah.edu/ubuntu jammy-updates InRelease
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 155.98.64.89 443]
W: http://ubuntu.cs.utah.edu/ubuntu/dists/jammy-updates/InRelease: No system certificates available. Try installing ca-certificates.
These messages don't make it completely obvious what the problem is,
and it's also a rather obscure setting; you have to carefully read the
Dockerfile to find it.
Due to issues like this, and changing mirrors over time, it's best
just to drop attempts to use a specific mirror and use whatever the
default you get for archive.ubuntu.com etc. With modern CNDs, this is
likely to be *faster* than a mirror, anyway.
The package downloads generally happen only once per host, anyway,
since Docker will keep not only the final image, but also the layers
used to generate it: if the final image is deleted or anything in the
Dockerfile after the OS package updates is changed, these cached
layers will be used.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ubuntu.cs.utah.edu mirror appears to be obsolete; trying to use it produces error messages along the lines of:
These messages don't make it completely obvious what the problem is, and it's also a rather obscure setting; you have to carefully read the Dockerfile to find it.
Due to issues like this, and changing mirrors over time, it's best just to drop attempts to use a specific mirror and use whatever the default you get for archive.ubuntu.com etc. With modern CNDs, this is likely to be faster than a mirror, anyway.
The package downloads generally happen only once per host, anyway, since Docker will keep not only the final image, but also the layers used to generate it: if the final image is deleted or anything in the Dockerfile after the OS package updates is changed, these cached layers will be used.