Add apt-get update to avoid using invalid cached metadata#997
Merged
Conversation
When running 'apt-get install' without doing 'update' in a github runner, the runner might try to use it's cached metadata of the apt repository, which might be out of date and cause the CI to fail.
gerrod3
approved these changes
Dec 19, 2025
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
2 participants
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.
When running 'apt-get install' without doing 'update' in a github runner, the runner might try to use it's cached metadata of the apt repository, which might be out of date and cause the CI to fail.
We saw this happen recently on pulp_ostree, which is a plugin that uses more system dependencies: the apt-get install would try to get (for example)
uuid-dev-1.0.0-ubuntu6.3but the deb repository would only have the latestuuid-dev-1.0.0-ubuntu6.4