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

DOCKER_HOST setting in v1.23.0+ not working correctly with Podman #3766

Closed
McClunatic opened this issue Dec 12, 2022 · 1 comment
Closed

Comments

@McClunatic
Copy link

I've been using the guidance in this comment to configure VS Code Docker to use Podman instead. It's worked perfectly! Unfortunately, the changes made in deprecating docker.host (see #3539) have led to issues.

Below is a screenshot of my Docker pane running v1.22.2.

image

If I upgrade to v1.23.0+, whether accepting the automatic migration of settings in the process or configuring them manually, I'm instead faced with the below.

image

Here's a shot of my environment settings in v1.23.2.

image

If it's helpful, I did check for debugging information in the Docker Output tab, but it is empty after upgrading to v1.23.2 and configuring settings. When I revert back to v1.22.2, set docker.host, and visit the Docker pane, I can see the following in the Docker Output tab:

The Docker extension will try to connect to 'unix:///run/user/1000/podman/podman.sock', via context 'default'.

Please let me know if I can provide any more information to help investigate and resolve this! Thanks!

@bwateratmsft
Copy link
Collaborator

This is a known issue. With 1.23.0, we began using the CLI exclusively for communicating with Docker, instead of a combination of the CLI and the HTTP API. While their respective HTTP APIs are nearly identical, the CLIs are more divergent, and Podman requires some more Podman-specific code that we haven't written yet. We're tracking that in #3241 (and I'll resolve this as a dupe of that).

The simplest workaround is going to be to roll back to Docker extension version 1.22.2. You can do so by running the command "Extensions: Install Specific Version of Extension..." in the command palette.

@bwateratmsft bwateratmsft closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2022
@microsoft microsoft locked and limited conversation to collaborators Jan 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants