fix(install): docker install failure when containerd.io candidate is missing from Docker repo #43
Conversation
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
When apt resolves a newer containerd.io version from Docker's repository metadata but the .deb file is not yet available (or temporarily missing) on the Docker CDN, the install fails with 404 errors. This adds a fallback strategy that: 1. Attempts the normal Docker install (unchanged behavior) 2. If it fails, refreshes apt metadata and enumerates available versions 3. Retries installation by pinning each available version (newest to oldest) This handles transient Docker repo/CDN sync issues gracefully without hard-coding a specific containerd version.
BenderV
changed the title
BenderV
changed the title
BenderV
changed the title
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.
note: generated by AI, but solved my issue.
Root issue
On Debian/Ubuntu systems, the installer occasionally fails during Docker installation with a
404 Not Founderror when fetchingcontainerd.io.This happens when:
aptresolves a newer containerd.io version from Docker's repository metadata.debfile is not yet available (or temporarily missing) on the Docker CDNIn that state, repeated
apt-get install containerd.ioattempts always fail, even though older, valid versions are still available in the same repository.This is a known class of issue during Docker repo syncs and CDN propagation delays.
Proposed fix
Make Docker installation resilient to missing containerd.io artifacts by adding a fallback strategy:
Attempt the normal Docker install using
apt(unchanged behavior in the healthy case)If it fails:
containerd.ioversions viaapt-cache madisonSucceed as soon as a valid version is found
This ensures:
.debis unavailableWhy this approach
User impact
404 Not Founderrors during Docker setup