-
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
Automatically open in container #2900
Comments
Thanks for the suggestion! To verify, would you be looking for something like this:
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 |
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. |
What do you mean by:
Is this a setting? an extension? |
@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 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 |
@jchallenger This is what I came here to say. |
Yes, please! Edit: See #5428
|
Something like |
It is already there. You can run:
|
For reference, this requires the devcontainer-cli |
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. |
@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 |
Whatever happened to this? I'm building an internal tool for my team and this would be super handy. |
See also #2133 |
Another workaround: |
Hey guys, although we can do it using the devcontainers CLI I would like to do it on a more global way, Is there a change we will get a setting for this? |
Yes, the hope would be to have a VSCode JSON configuration to have the editor automatically reload if there's a DevContainer or even start up automatically. |
Please add a setting for always attempting to open in a container if a project contains the .devcontainer folder.
The text was updated successfully, but these errors were encountered: