-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add open
command to @vscode/dev-container-cli
#5957
Comments
There was a version in the past that supported the $ devcontainer --help
devcontainer <command>
Commands:
devcontainer open [path] Open a dev container in VS Code
devcontainer build [path] Build a dev container image
Options:
-h, --help Show help [boolean]
--disable-telemetry Disable telemetry [boolean] [default: false] However, a few days ago and after following the instructions to install it on a new Ubuntu distro (WSL2), the output of $ devcontainer --help
devcontainer <command>
Commands:
devcontainer build [path] Build a dev container image
Options:
-h, --help Show help [boolean]
--disable-telemetry Disable telemetry [boolean] [default: false] As you can see it list only The |
@ManfredLange There are two ways to install the CLI: As part of the Remote-Containers extension and as an NPM package. Currently the NPM package does not support When you use the CLI installed as part of Remote-Containers, the |
I just wrote a similar issue before searching and finding this - doh. It didn't feel right to dump my bug report in the issues after finding this, but let me know if you think it'd help to get it documented. PS. I actually found #2900 before this |
The installation method via the Remote-Container extension in fact installs it..... On my Windows host. However, I am using WSL2 (Ubuntu 20.04) installed and that is where I want to install the devcontainer-cli. The extension doesn't do that. And when installing via So, while it's useful to know that the devcontainer-cli can be installed via the extension, it doesn't appear in WSL2. |
The installation method via the Remote-Container extension in fact installs it..... On my Windows host. However, I am using WSL2 (Ubuntu 20.04) installed and that is where I want to install the devcontainer-cli. The extension doesn't do that. And when installing via So, while it's useful to know that the devcontainer-cli can be installed via the extension, it doesn't appear in WSL2. It does appear, though, when I restart the computer. So the following seems to work:
This recipe applies to this set up:
|
@ManfredLange Thanks, that works! In my case, it was enough to restart the WSL with |
In my case, after restarting WSL2, running
Has anyone debugged that symptom? |
I built my own code --devcontainer ~/repos/myproject It works for when VS Code is running on Linux, when running from within a remote SSH session (in or out of the vscode integrated terminal) and even within a remote tunnel session. https://github.com/felipecrs/dotfiles/blob/master/home/dot_local/bin/executable_code It is immensely useful and timesaving for me, so I expect other people to benefit from it too. Simply install it to your WindowsTerminal_yAF02SU1CR.mp4 |
This issue is a follow-up of #5415 (comment).
Now the
devcontainer
cli is available to be installed from npm withnpm install --global @vscode/dev-container-cli
, but it's missing theopen
command.My use case is to have it installed as part of my dotfiles, so that I get the devcontainer command installed every time I bootstrap a new computer with my dotfiles installation script (which also manages to install VS Code, by the way).
However, I use a similar dotfiles experience as a managed development environment for the my team, and there, I have a guide where I tell them to:
devcontainer open
itBut it would be too cumbersome if I had to write instructions like:
And then get back to the part where
devcontainer open
would actually work.The text was updated successfully, but these errors were encountered: