-
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
Direct open VS Code Remote Containers workspace path with code
CLI?
#4684
Comments
When working with a remote container on my WSL machine, I run This seems like a waste of time. It would be better if running |
See #2133 for what I believe is a related dupe issue. |
So you can almost do this right now:
by replacing The only thing I haven't worked out is the cluster - it uses whatever is the default context in |
@emcake The cluster can currently not be specified. Could you open a feature request for us to track this? |
ah - I was looking for a
this is 🔥🔥🔥 |
@rzhao271 do you know what the proper way to specify the k8s context (from #4975) in the above URL specification is? that wasn't clear to me in #4975 and the issue was locked before I had a chance to respond. I'm guessing its something like |
@kwlzn It is |
@chrmarti thanks for confirming! |
to close the loop on this, we've implemented an experimental feature flag in our company-wide DS/ML Jupyter Notebook tooling that allows users to trivially attach VS Code Remote to their Jupyter Notebook instances. this feature has already been met with a warm reception by our eager adopters and we'll continue to pilot this internally. thanks a ton for the response and support here, much appreciated. |
Glad you found a fix but I'd still consider this issue a valid feature request for a simplified process via the VSCode CLI. |
We are tracking the more general request here: #2133 |
A very common tooling scenario we have at Twitter is to e.g.:
[<$datacenter>/]<$namespace>/<$job_name>-<$environment>
that we can use to reference that jobopen $proxy_url/$job_key
which completes the launch lifecycleI think in the tooling use case of using VS Code Remote as a remotely attached front-end, we would love it if there were some way to use the
code
CLI to automatically connect to containers running in a Kubernetes cluster.is this possible today? if not, could it be made possible?
for a k8s pod like:
being able to open a path inside it in one CLI invocation, e.g.:
would make VS Code front-end integration incredibly composable for us and likely others using VS Code Remote Containers.
The text was updated successfully, but these errors were encountered: