fix: update Docker workflow target to match new Dockerfile structure #2000
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
This PR fixes a critical issue in the Docker workflow where the build target doesn't match the actual Dockerfile structure, causing production deployment failures.
Issue
The
docker.yamlworkflow was trying to build:target: bolt-ai-production(doesn't exist in current Dockerfile)Fix
Updated to use the correct target name:
target: runtime(matches actual Dockerfile stage)Current Dockerfile Structure
The Dockerfile has these stages:
build- Build stage with dependencies and compilationruntime- Production runtime stage ⭐ (This is what we need)development- Development stage with dev toolsImpact
Before: Docker builds would fail with
ERROR: target stage "bolt-ai-production" could not be foundAfter: Docker builds succeed using the correct
runtimetargetTesting
This fix ensures:
Related
This complements PR #1999 which fixed the Dockerfile syntax errors and added Docker build validation to CI.