-
Notifications
You must be signed in to change notification settings - Fork 304
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
'Attach Visual Studio Code' does nothing, throws no error, no logging #5100
Comments
Is there anything in |
That command doesn't appear to do anything (3. above). There's no appropriately-named option in the Output dropdown either. |
Is there anything in the Extension Host output channel? It sounds like the extension might fail to activate, but that would usually show an error notification. |
On launching vscode, there's a bunch of loads and activations in that channel, with the two remote-related lines being
When I click on the Kubernetes icon on the LHS, there're a few more:
But expanding the 'pods' list and clicking 'Attach to Visual Studio Code' generates no further logs; just the 'Activating Extensions' spinner in the status bar for a few seconds then nothing. |
Is this pretty much DOA then - you've not seen anything like this, and there's no way for me to get more information on what's causing the behaviour? |
I'm having the same issue. When I've setup the Kubernetes extension locally I get the following error when trying to Attach to a running pod:
When I'm SSHed into a server and try the same via the Kubernetes extension in that window I don't receive an error message, and nothing happens. I can use the Kubernetes extension normally otherwise (so start a terminal, view logs, etc). |
I just got it working for me - the logs were showing this
and in my case I'm using EKS so I ran the following
and now the Attach context menu item works. |
Is there a better way to determine which cluster is shown in the Kubernetes viewlet than |
@caesarnine Which logs? I'm getting the same behaviour - works locally but silent failure when I try in a remote SSH session. Running |
Attaching to a Kubernetes pod while connected with Remote-SSH is currently not supported. I'll make sure the action is not show in the context menu in this case. |
I think that @caesarnine 's error is subtly different from the one @adambozson and I are seeing. I still am not getting any logs at all, and it's not fixed by Adam, here are some less-than-usual things about my setup - mind telling me if you match on any?
|
@andyljones How are you connecting to AWS? Are you in a local VS Code window when you run |
Yes, I'm in a local VS Code window. I'm connecting through a script that starts with SSO and ends with a bunch of For reference, the other commands in the Kubernetes right-click menu work - like |
Adding logging to help track this down. (Will be in the next version for VS Code Insiders.) |
Still nothing. Same extension host logs as before, same spinner when I 'Attach Visual Studio Code', and no further logs to go with it. Insiders version
I suspect this might be hard to believe, so I've attached a little vid so we can see if I'm doing anything daft. output.mp4And here are the logs that are present, all of which appear before clicking 'Attach Visual Studio Code':
|
@andyljones Could you retry with Remote-Containers 0.195.0 and check the container log ( |
Updated to 0.195.0 and tried e: I've just noticed that the 'Runtime Status' page of Remote - Containers shows as 'Not yet activated', and going to the Remote Explorer the containers spinner runs permanently. I wonder if this something about my Docker install. Let me try some experiments... |
b i n g o I had A minimal example is
which hangs on my Mac. Have that variable set somewhere that vscode can see it and loading the extension (presumably) times out and fails. Anyway now I've removed that line from my zshrc, Attach works fine! Thanks so much for your patience! |
And just checked my
calls, which I reckon are the root of this. |
Steps to Reproduce:
Does this issue occur when you try this locally?: N/A
Does this issue occur when you try this locally and all extensions are disabled?: N/A, can't do this with no Kubernetes extension
I suspect there might be a million reasons for this, and I'm working in a 'heavy' environment that'd be difficult to offer you a minimal reproduction for. So rather than giving you every detail of my setup, I think it's better to ask: how'd I go about getting enough information to isolate the problem? I haven't spotted any obvious log level settings.
(Aside: I saw something somewhere that said the 'Attach Visual Studio Code' menu entry is your folks' turf rather than the vscode-kubernetes-tools folks', but say if I've got that wrong)
The text was updated successfully, but these errors were encountered: