Repository navigation
Pin pipenv in the Docker build - #8
Merged
Merged
Conversation
The Docker build installed the newest pipenv. pipenv 2026.9.1 requires a newer packaging than the one Debian installs with python3-pip, and pip can't uninstall Debian's copy (no RECORD file), so the build failed on a merge that didn't touch anything Python-related. Pin pipenv so new releases can't break unrelated builds, and pass --ignore-installed so pip installs its own packaging next to Debian's instead of trying to remove it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XuPs3nkTaDwZGoCD8oKKEV
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
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
The "Publish Docker image" run after the #7 merge failed at
Dockerfile:38:The change in #7 (one
.vuefile) didn't cause this. The Dockerfile installs pipenv without a version:packagingthan the one Debian installs withpython3-pip.Change
Pipfile.lock.--ignore-installedmakes pip install its ownpackagingalongside Debian's instead of trying to remove it.Everything else in the build is left as is:
Pipfile.lock(--deploy --ignore-pipfile).yarn.lock.node:24-trixie-slimbase image stay unpinned so they keep getting Debian security updates.Testing
I couldn't run a Docker build in my environment. The "Check Docker" workflow runs on this PR because it touches
Dockerfile, and that run is the test.🤖 Generated with Claude Code
https://claude.ai/code/session_01XuPs3nkTaDwZGoCD8oKKEV
Generated by Claude Code