Mohsen Ansari
Mohsen Ansari
The PR that fixes this issue is merged. It will be included in the next version of Devbox release. Once the new release is out I will message here letting...
@tclasen With the release of devbox v0.10.4 this issue is resolved.
@s0rbus With the release of devbox v0.10.4 this issue is resolved.
Hey @ts0818 can you expand on what you mean by devbox services? Are you running a web server as a devbox service locally? or is it hosted somewhere else? We...
@ts0818 oh I see. Devbox service and devbox shell don't create a virtualization layer like Docker to run your processes. What you're running in a devbox service is running on...
@em-jones apologies for late response, I missed this message somehow. The `Reopen in devbox shell environment` command doesn't work if your VSCode is connected to a remote environment. The reason...
Hey @BeyondEvil thanks for reporting this. From the logs it seems like VSCode sets up the communication with devbox process successfully and devbox process computes the environment. What fails is...
@hbouhadji I can add this fairly quick. Can you expand on what is your desired outcome with regards to .env files and the vscode extension?
@W1M0R Thank you for pointing it out. I hid those spam comments and reported the users to github.
@W1M0R For devconainer support, we use devbox itself to setup the environment inside the container. Given most containers are Linux based, that shouldn't cause a problem even if the container...