Local Deployment Not Working
Describe the bug Installation process fails during Docker build with multiple issues:
-
docker-composecommand not found - Bundler deployment mode error during build
To Reproduce Steps to reproduce the behavior:
- Try to use
docker-composecommand:
docker-compose build
# Results in: zsh: command not found: docker-compose
- After correcting to
docker compose, the build fails:
docker compose build
# Results in bundler deployment error
Expected behavior
- Docker commands should work with proper syntax (
docker composeinstead ofdocker-compose) - Docker should successfully build the images and start the containers
All documentation should be updated to use docker compose instead of/or docker-compose. (https://stackoverflow.com/questions/78769459/command-not-found-docker-compose-after-docker-4-32-0-update)
Environment:
- OS: macOS
- Docker Desktop version: 4.37.2
- Architecture: ARM64 (Apple Silicon)
Error Details
- Command syntax error:
zsh: command not found: docker-compose
- Build error:
ERROR [multiwoven-worker build 28/34] RUN bundle install && rm -rf ~/.bundle/ "/usr/local/bundle"/ruby/*/cache "/usr/local/bundle"/ruby/*/bundler/gems/*/.git && bundle exec bootsnap precompile --gemfile:
0.438 You are trying to install in deployment mode after changing
0.438 your Gemfile. Run `bundle install` elsewhere and add the
0.438 updated Gemfile.lock to version control.
Attempted Solutions
- Updated commands to use
docker composeinstead ofdocker-compose - Tried running
bundle installin both server and integrations directories - Attempted to build with
TARGETARCH=arm64flag - Cleared Docker volumes with
docker compose down -v - Rebuilt without cache using
docker compose build --no-cache
Additional context The project contains two Gemfiles:
- ./server/Gemfile
- ./integrations/Gemfile
Both are failing to install due to bundler deployment mode restrictions. Local bundle installation fails due to bundler version mismatches (2.4.1 and 2.5.10 required but not found).
Hey @DVDH-000, we're looking into this issue. If you've found a solution, please let us know. There's already a PR in place for the docker syntax issue. #621.