Skip to content
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.96 (again) does not connect to the container #10562

Open
devaex opened this issue Dec 13, 2024 · 3 comments
Open

Version 1.96 (again) does not connect to the container #10562

devaex opened this issue Dec 13, 2024 · 3 comments
Assignees
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster

Comments

@devaex
Copy link

devaex commented Dec 13, 2024

  • VSCode Version: 1.96
  • Local OS Version: Linux Mint 22 Cinnamon
  • Remote OS Version: Ubuntu 22
  • Remote Extension/Connection Type: Containers/Distrobox

It was already resolved and it happened again.

The reason seems to be that vs code are not reading the settings to use podman an try to use docker.

See this issue for reference:
#10426

The same workarround can be used to solve temporarily:

  • F1 -> Preferences: Open User settings (JSON).
  • Put "dev.containers.dockerPath": "podman" in settings.
  • Vscode warned that this configuration is out of scope but I ignored it.
  • Try to attach to the container, and the connection was made as always.
@chrmarti
Copy link
Contributor

To use Podman you currently have to set that setting. That's expected.

If this works in VS Code Insiders (if I read the other issue correctly), it probably has podman in its settings (VS Code stable and Insiders have separate settings).

@chrmarti chrmarti added the info-needed Issue requires more information from poster label Dec 16, 2024
@devaex
Copy link
Author

devaex commented Dec 17, 2024

I don't use VS Code insiders. I installed this version just to test if the problem had been resolved in this version, and it was.

Then I returned to the regular version where the problem was resolved in the previous update.

Now after the last update this has happened again.

Image

Version: 1.96.0
Commit: 138f619c86f1199955d53b4166bef66ef252935c
Date: 2024-12-11T02:29:09.626Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 6.8.0-51-generic

@devaex
Copy link
Author

devaex commented Dec 17, 2024

To solve, I need to place the configuration in User settings, where VS Code itself informs me that it is not the correct place.

This also makes it clear that the configuration made in Application settings is being ignored, as it does not work without the configuration in User Settings.

User settings

Wrong place, but works

Image

Application Settings

Correct place, but don't works

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants