You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Here's a shot of my environment settings in v1.23.2.
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!
The text was updated successfully, but these errors were encountered:
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.
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.
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.
Here's a shot of my environment settings in v1.23.2.
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:Please let me know if I can provide any more information to help investigate and resolve this! Thanks!
The text was updated successfully, but these errors were encountered: