Use bullseye base image for server Docker builds#13
Open
nesvet wants to merge 1 commit into
Open
Conversation
Debian buster apt mirrors are gone; bullseye keeps Docker image builds working. Install git for optional pip installs from VCS during development.
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.
Summary
Debian buster apt mirrors are EOL;
python:3-busterserver image builds fail on fresh CI runners.This PR switches the server Dockerfile to
python:3.9-slim-bullseye, uses the modern Docker apt keyring layout, and installsgitso contributors canpip installthe library from a VCS URL during local testing.Independent of feature PRs #9–#12 — safe to merge on its own while other work is in review.
Test plan
docker build -t nojava-ipmi-kvm-server:test .Reproduced locally with bullseye base image; container builds and serves the login page.