Description
A clear and concise description of the problem.
Environment
- Editor: VSCodium
- Extension version: 0.3.1
- OS: Linux (wsl)
- Docker version: 29.4.1
devcontainer config
Paste relevant parts of .devcontainer/devcontainer.json (image, remoteUser, post*Command):
Steps to Reproduce
- Open folder in WSL with the open-remote-wsl by jeanp413
- create the .devcontainer/devcontainer.json
- use any command like "Open Devcontainer Configuration" or "Rebuild and Open"
Expected Behavior
I would expect for the extension to behave as if i was in a native linux environment
Actual Behavior
it complains that it doesn't find the json
Logs
From the "Codium Devcontainer" output channel:
Running postStartCommand in remote terminal...
postStartCommand: /sbin/entrypoint.sh true
Error: No devcontainer.json found
Error: No devcontainer.json found
Error: No devcontainer.json found
Error: No devcontainer.json found
Additional Context
I used to use this very configuration on Microsoft's VSC but using the proprietary implementation by Microsoft.
I also noticed that when I open the folder it does find the postStartCommand and log it. This means that for a brief moment it is able to find the right path.
Description
A clear and concise description of the problem.
Environment
devcontainer config
Paste relevant parts of .devcontainer/devcontainer.json (image, remoteUser, post*Command):
{ "image": "buildenv", "postStartCommand": "/sbin/entrypoint.sh true", "remoteUser": "builder", }Steps to Reproduce
Expected Behavior
I would expect for the extension to behave as if i was in a native linux environment
Actual Behavior
it complains that it doesn't find the json
Logs
From the "Codium Devcontainer" output channel:
Additional Context
I used to use this very configuration on Microsoft's VSC but using the proprietary implementation by Microsoft.
I also noticed that when I open the folder it does find the postStartCommand and log it. This means that for a brief moment it is able to find the right path.