Opt-out of Phased Updates in apt. #667
Merged
Conversation
This file contains 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
Docker containers are built using a succession of images, each of of which is created by running an intermediate container and saving the result. These individual containers can end up with different information that puts them in different "phases" of the apt phased update rollout. When combined with a phased update for a set of binary packages that all rely on matching versions, it can create an unsatisfiable condition where an earlier binary from the source package was installed in the "ahead" phase and a later package is installed "behind". Phased updates only became supported in apt 2.1.16 released in Ubuntu 21.04 so this was not an issue for us prior to Ubuntu Jammy.
|
🐧 |
|
I haven't gone back to find the record yet but were apt installation issues on ARM hosts earlier which we thought at the time were problems with apt mirror synchronization but may actually have been an earlier less egregious version of this problem. |
These results (50:50) are not encouraging since any time we bust the docker cache we have a chance of landing all "behind" or all "ahead" and being able to build. So something about this change is insufficient and I kept "getting lucky" when testing it locally. |
|
🐧 |
Blast545
approved these changes
Jun 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Docker containers are built using a succession of images, each of of which is created by running an intermediate container and saving the result.
These individual containers can end up with different information that puts them in different "phases" of the apt phased update rollout.
When combined with a phased update for a set of binary packages that all rely on matching versions, it can create an unsatisfiable condition where an earlier binary from the source package was installed in the "ahead" phase and a later package is installed "behind".
Phased updates only became supported in apt 2.1.16 released in Ubuntu 21.04 so this was not an issue for us prior to Ubuntu 22.04.