-
Notifications
You must be signed in to change notification settings - Fork 306
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
Version 1.95 does not connect to the container with distrobox #10426
Comments
Please append the Dev Containers log from when this happens. ( |
Updated to last version and same error. Version: 1.95.1 Dev container settings pointing to podman: Try to Attach to running container, it lists ubuntu container: But inform that ubuntu container not exists: Dev container logs
The logs stop at this point and no new feedback is returned. |
Some more info:
|
Logs of version 1.94 that connect with success.
|
Mentioned this in a comment on an issue in the main VSCode GitHub, but do you have a profile enabled? For me this issue appears to be because the “applies to all profile” settings appear to not be getting applied across profiles in 1.95, so 1.95 tries to take your docker path from the profile (which is empty, so it defaults to docker) and not the top level. If this applies to you as well, switching back to the default profile works around the issue (at least it does for me), and editing the profile’s .json file and putting the relevant top-level settings in there also works (you just have to remember to take them back out once the issue is fixed). |
Great find. I confirm that this solves the problem and it must certainly be something related to the scope of the settings. What I did:
Thank you for mentioning the answer in this issue. |
I am able to repro a similar settings issue in the Remote - SSH extension (doesn't repro in |
@devaex @mlawson27 The fix for microsoft/vscode#232602 is available in today's VS Code Insiders (https://code.visualstudio.com/insiders/). Could you give that a try and let us know if it fixes the problem? Thanks! /cc @sandy081 |
@chrmarti I confirm that the Insiders version fixed the problem. Thanks for attention. |
This error returned in version 1.96. The same workarround can be used:
|
Opened new one: And closing this. |
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
It worked perfectly until version 1.94.
Nothing was done other than updating vscode to 1.95
What was attempted to solve:
Finally I uninstalled version 1.95 and installed version 1.94 and it worked as usual again.
The text was updated successfully, but these errors were encountered: