-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Closed
Labels
kind: bugSomething isn't workingSomething isn't working
Description
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
https://github.com/livingforjesus/turbo-docker-prune-bug-repro
Which canary version will you have in your reproduction?
canary
Environment information
visiononyeaku@visions-Laptop bug-repro % turbo info
• turbo 2.8.11-canary.9
CLI:
Version: 2.8.11-canary.9
Path to executable: /Users/visiononyeaku/Desktop/Work/Rip-Tech/bug-repro/node_modules/.bun/turbo-darwin-arm64@2.8.11-canary.9/node_modules/turbo-darwin-arm64/bin/turbo
Daemon status: Not running
Package manager: bun
Platform:
Architecture: aarch64
Operating system: macos
WSL: false
Available memory (MB): 7778
Available CPU cores: 10
Environment:
CI: None
Terminal (TERM): xterm-256color
Terminal program (TERM_PROGRAM): vscode
Terminal program version (TERM_PROGRAM_VERSION): 1.107.0
Shell (SHELL): /bin/zsh
stdin: false
Expected behavior
I expect the app to run inside the docker prune just like it runs in the regular app
Actual behavior
The app doesn't run in the docker prune and throws an error because of grouping of incompatible packages due to wrong lockfile generated
To Reproduce
Clone https://github.com/livingforjesus/turbo-docker-prune-bug-repro- Run
chmod +x bug-repro.sh - Run
./bug-repro.sh - Error occurrs
Additional context
I'm using turbo prune --docker.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind: bugSomething isn't workingSomething isn't working