vscode-remote-release
vscode-remote-release copied to clipboard
Automatically open in container
Please add a setting for always attempting to open in a container if a project contains the .devcontainer folder.
Thanks for the suggestion! To verify, would you be looking for something like this:
- If the notification appears telling you that you can reopen in container, there's an option that says something along the lines of "always reopen".
- If you click it, from that point forward, any time a folder is opened in VS Code with a devcontainer.json present, it just does it.
Moving to the vscode-remote-release repo where we're tracking extension feedback.
@Chuxel EXACTLY.
Currently I flip between different projects (8-10 at a time) and each time I have to wait for the popup and click "Reopen in Contanier" manually.
Hi @turowicz , I'm not sure if you know, but on Windows you can at least "pin" container-projects. This way they are immediately openable from the icon on the taskbar and the start menu. Maybe this helps.
@yngwi I'm on Ubuntu 20.04 and OSX
@yngwi I'm on Ubuntu 20.04 and OSX
I'm sorry, I didn't realize.
Any update on this? Would like to have this feature too.
I have switched to "Open Repository in Container". No longer a problem for me.
@turowicz
What do you mean by:
switched to "Open Repository in Container"
Is this a setting? an extension?
@ldiebold

@turowicz Ahh I see. Still kind of a workaround. Maybe we can find an extension that allows us to run a command when the editor has loaded.
@ldiebold if using Docker For Windows, that way the filesystem is much faster and you can get 10x on build times.
@turowicz I'm on Linux 😊 It's not so much a speed issue, more of a convenience.
It's lightning fast, but I just don't want to click the button every day 🤣
@ldiebold I'm on Linux too, you can still get 10% off build time.
@turowicz now I'm just confused. You can get Docker for windows on Linux?
No, you can have more workstations.
LOL
Would be great if I could open into a devcontainer from the command line, like code . --devcontainer
Would be great if I could open into a devcontainer from the command line, like
code . --devcontainer
@jchallenger This is what I came here to say.
Would be great if I could open into a devcontainer from the command line, like
code . --devcontainer
Yes, please!
Edit: See #5428
🔴 Integrate the Dev Container CLI with the VS Code CLI, e.g. code --open-in-devcontainer .
Something like code . --devcontainer would be fantastic. The request of this feature support for the CLI is really a testament to the pervasiveness of this development strategy!
Looking forward for this code . --devcontainer option.
As stated before, something similar was on the #5428 iteration, but it wasn't implemented, and wasn't moved to the next iteration plan (#5552).
It is already there. You can run:
devcontainer open .
It is already there. You can run:
devcontainer open .
For reference, this requires the devcontainer-cli
I'm not sure if you know, but on Windows you can at least "pin" container-projects. This way they are immediately openable from the icon on the taskbar and the start menu. Maybe this helps.
Fabulous suggestion. (I'm using StartIsBack for Windows 7-style menus). I can pin the dev-container versions of projects:
Also want to mention: VSCode in-container development is the greatest thing since sliced bread!
Does anyone know how to to tell code to open specific folder using wsl from the command line? That is essential for testing purposes.
Does anyone know how to to tell code to open specific folder using wsl from the command line? That is essential for testing purposes.
@ssbarnea, you can just cd to the folder and type "code ."
(or presumably "code directory-name")
However, when code launches you get an option to "Open in dev container" if it has the write folder structure. Are you asking if you can bypass that and go straight to opening in container?
The solution is code --remote wsl+Ubuntu /mnt/c/Users/johndoe/c/myrepo and would work if you already have the wsl-remote extension installed. The path given must be the Unix one, so you may need to convert Windows path to Unix. Keep in mind that drive letter becomes lowercase but other things keep the case.
Whatever happened to this? I'm building an internal tool for my team and this would be super handy.
See also #2133
Another workaround: File > Save Workspace As .... On Windows just double click the file. But seems to break if you add additional folders to the workspace.