Skip to content

Conversation

@Stijnus
Copy link
Collaborator

@Stijnus Stijnus commented Sep 16, 2025

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.yaml workflow 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:

  1. build - Build stage with dependencies and compilation
  2. runtime - Production runtime stage ⭐ (This is what we need)
  3. development - Development stage with dev tools

Impact

Before: Docker builds would fail with ERROR: target stage "bolt-ai-production" could not be found
After: Docker builds succeed using the correct runtime target

Testing

This fix ensures:

  • ✅ Production Docker builds work correctly
  • ✅ Container deployments succeed
  • ✅ CI/CD pipeline doesn't break on Docker builds
  • ✅ Matches the fixes already applied to CI validation

Related

This complements PR #1999 which fixed the Dockerfile syntax errors and added Docker build validation to CI.

- Change target from bolt-ai-production to runtime
- Matches the actual stage name in the current Dockerfile
- Prevents Docker build failures in production deployments
- Fixes target stage 'bolt-ai-production' could not be found error
@Stijnus Stijnus merged commit 437d110 into stackblitz-labs:main Sep 16, 2025
16 checks passed
@Stijnus Stijnus deleted the fix-docker-workflow-upstream branch September 19, 2025 09:07
ChiR24 pushed a commit to ChiR24/bolt.diy that referenced this pull request Sep 25, 2025
…tackblitz-labs#2000)

- Change target from bolt-ai-production to runtime
- Matches the actual stage name in the current Dockerfile
- Prevents Docker build failures in production deployments
- Fixes target stage 'bolt-ai-production' could not be found error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant