fix(docker): Remove conflicting Python symlinks#1
Merged
Conversation
added 2 commits
February 19, 2026 16:43
The ln commands were trying to create symlinks to python3.11/3.12/3.13 but python3 is already python3.11 in bookworm-slim, causing the build to fail with 'are the same file' error. Removed unnecessary symlinks - python3 is already available and works for Lambda execution.
- Implement FromStr trait for ExecutorMode instead of custom from_str - Add #[allow(dead_code)] to WarmContainer.runtime (used for tracking) - Apply rustfmt to align with style guidelines
added 3 commits
February 19, 2026 16:57
Also fix rustfmt formatting in test
Function kept for API consistency but currently unused
Function kept for API consistency but currently unused
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.
Problem
The Docker build for releases was failing with:
Root Cause
The
Dockerfile.releasewas trying to create symlinks:python3.11 → python3python3.12 → python3python3.13 → python3But in
debian:bookworm-slim,python3is alreadypython3.11, so the firstlncommand failed.Solution
Removed the unnecessary symlink commands. The base image already provides
python3which works perfectly for Lambda execution — we don't actually need multiple Python version aliases.Testing
python3directly)Fixes the failed release workflow for v0.1.0.