docker: Remove Arch support from Debian-based container #484
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
It turns out that trying to bootstrap an Arch system from Debian-packaged tools is quite hard since Arch moves much quicker than Debian Bookworm. Any upstream Arch churn can cause the Debos container build to break (this has happened twice now). Since this really is an anti-pattern in Debos - we suggest building an OS image from the packages which make that OS - remove the Arch bits from the Debian Dockerfile to stop breakages. The hope is as time goes on we can create a separate Arch-based Dockerfile for Arch support. Link: #483 Signed-off-by: Christopher Obbard <[email protected]>
| make && \ | ||
| rm -rf /var/lib/apt/lists/* | ||
|
|
||
| RUN git clone https://gitlab.archlinux.org/archlinux/archlinux-keyring && \ |
There was a problem hiding this comment.
the problem is not so much arch; the problem is trying to rebuild their keyring. The debian packaging for this simply uses the prebuild keyrings instead (part of every release)
There was a problem hiding this comment.
right so it seems like a prebuilt version is available at https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/releases/20240208 , but there is no endpoint for latest release.
I could either:
- download the git repo, use the latest tag & hope it has a release
- use the gitlab API to get the latest release (e.g https://forum.gitlab.com/t/gitlab-api-get-latest-release-version/48608)
- revert the arch bits in the docker container and build a separate docker image for arch
My preference was to do 3, but I could look at 2.
FYI the debian package archlinux-keyring is far too old (currently 0~20221220-2~bpo11+1 in backports)
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.
It turns out that trying to bootstrap an Arch system from Debian-packaged tools is quite hard since Arch moves much quicker than Debian Bookworm. Any upstream Arch churn can cause the Debos container build to break (this has happened twice now).
Since this really is an anti-pattern in Debos - we suggest building an OS image from the packages which make that OS - remove the Arch bits from the Debian Dockerfile to stop breakages. The hope is as time goes on we can create a separate Arch-based Dockerfile for Arch support.
Link: #483