You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using devbox generate devcontainer to generate the .devcontainer and the associated Dockerfile.
When I'm launching the devcontainer using VSCode, I'm facing this issue : Poetry could not find a pyproject.toml file in /code or its parents
I saw that the Dockerfile having reference to the code folder but I don't have it and the Poetry setup is working perfectly my local environment as you can see below :
I can duplicate the pyproject.toml file but ... i think it's not the right way to override this issue...
Expected Behavior (fix)
The Devcontainer must start and initialize devbox and poetry shell as well.
Additional context
devbox version -v 1 err 17:45:43
Version: 0.8.7
Platform: darwin_arm64
Commit: 525bb17ed665bb3066fbd3fb9bccec0aa961ecb7
Commit Time: 2024-01-23T19:15:31Z
Go Version: go1.21.5
Launcher: 0.2.1
The text was updated successfully, but these errors were encountered:
@spawnrider glad you found the solution. Apologies for that. I have made a PR to update our docs and generated dockerfile to notify that you should add your project files and directories.
Current Behavior (bug)
I'm currently using Devbox and Poetry to setup a tiny Python project.
I'm using devbox generate devcontainer to generate the .devcontainer and the associated Dockerfile.
When I'm launching the devcontainer using VSCode, I'm facing this issue :
Poetry could not find a pyproject.toml file in /code or its parents
I saw that the Dockerfile having reference to the code folder but I don't have it and the Poetry setup is working perfectly my local environment as you can see below :
I can duplicate the pyproject.toml file but ... i think it's not the right way to override this issue...
Expected Behavior (fix)
The Devcontainer must start and initialize devbox and poetry shell as well.
Additional context
The text was updated successfully, but these errors were encountered: