Integration with Visual Studio 2022

[iainwest]

Has anybody managed to get PodMan working with Visual Studio 2022? I have attempted and got warnings, after I changed some variables e.g. DOCKER_HOST to podman under wsl2 have now been presented with an Error response from daemon No such file or directory, OCI runtime attempted to invoke a command that was not found.

Just wondering if there are other variables I need to set?

[rhatdan]

If you run Podman directly does it work?

If you run docker with DOCKER_HOST set does it work?

[iainwest]

Running Podman directly, I am able to launch a container, I don't have docker desktop installed as I removed this before installing Podman.

After a little bit more trial and error, I reset WSL2 and performed the following steps, all from windows terminal

1. podman stop
2. podman machine rm podman-machine-default
3. podman machine init
4. podman start

The only other change since I started this was I am now running Visual Studio 2022 Version 17.6.0 Preview 1.0 with .Net 8 Preview 1 installed and my test container is targeting .Net 8.

I can only assume that my first attempt caused some corruption within the setup.

[VeselovAndrey]

Same issue for me. Win11 + VS 2022 latest + Podman Desktop. Also have a VS Code. All tooling can't see Podman (but it's running) and asking to install Docker. Are there any manual how to configure tooling?

[Cinorid]

@iainwest @rhatdan @VeselovAndrey
it's because the visual studio is trying to find docker.exe. the easiest way to fix this is to make a copy of podman.exe and name it docker.exe.

[rhatdan]

Could someone open an issue with visual studio to look for podman.exe as well?

[VeselovAndrey]

@Cinorid Didn't work for me. Only working way is to get "docker.exe" from Docker CE and add it location to the PATH env var.

[jeroen-mostert]

For others trying to make VS play nice with Podman, aside from copying podman.exe a little more work is needed to get it to work with podman-compose (much like Docker, it's hardcoded to look for docker-compose and moreover makes some assumptions that don't work for podman-compose). I've cobbled together a little wrapper for docker-compose at https://github.com/jeroen-mostert/vs-podman-wrapper , which also has instructions for getting the rest to work. A cleaner integration is certainly possible, but writing VS extensions is not in any way fun.

[gudge25]

any update?

[rhatdan]

Has anyone approached Visual Stodio to get them to work with Podman?

[gudge25]

so the solution is
1- Find out DOCKER_HOST
https://podman-desktop.io/docs/migrating-from-docker/using-the-docker_host-environment-variable
2- Downgrade Docker Extension to v1.22.2
3- 'Docker Host ' in 'Docker Extension' settings to unix://..../podman.sock (from step 1)
4- set 'Docker Path' in 'Docker Extension' to podman executive program example /usr/local/bin/podman

restart VS Code

[rhatdan]

I mean natively support Podman not in Docker compatibility mode.

[soerennielsen]

Also wanting to run podman with VS 2022.

It is however sadly a common problem in these threads that some people Tak about VS code and others VS 2022.

Two very different IDEs that share nothing in terms of tooling setup.

Thanks to original poster. Will try some of the steps here. For me the acceptance criteria is that I can start from VS 2022 and execute, debug (auto attach remote debugger) and we'll.. Build/package.

[pozy]

If anyone is interested, here's related feature request for Visual Studio (link). More votes - bigger chance VS team would implement it.

[GarretWayne]

Took a while and asked around, however the current working strategy for us is looking like this:

• Installed packages:
  • Docker.CLI
    • to communicate with Podman Daemon (that is in WSL)
  • Podman (can be Desktop or just "podman-machine" + "podman-cli")
    • desktop fully installed with WSL fully working
    • and a configured podman-machine

The idea behind the whole thing is Podman's API forwarding capabilities (see this section)
and the idea behind switching out the thin client that is used on windows to communicate with Podman's Daemon

Also if your "docker info" say something along the line as "IPV4 port-forwarding is disabled", you can use "sudo sysctl net.ipv4.ip_forward=1" to enable it. (Although a fair warning as all new podman-machines might require setting this manually at first launch).

This setup resulted in a fully working Visual Studio Container tab, and the Terminal to respond to all docker commands, whilst all containers are hosted in WSL by Podman.

[soerennielsen]

;) looking forward to it.

I got it somewhat working:

• Installed podman (followed their guide)
• symlinked docker.exe to podman.exe (windows) to make visual studio builds go the right place.

It works in visual studio (not code!), build + debugging. Container tools do not work and also it wants to start docker desktop initially.
Requires podman to be running (which will block docker desktop from running).
Clunky but working. There will likely be more details not working.

[tlunsfordCXP]

Any progress on this in recent months? I'm about to go down this rabbit hole and any new info would be helpful.

[GarretWayne]

Disclaimer:

• The short version should be the first approach to start with, as the long-one I did with a podman desktop first approach. However, the long approach is still heavily riddled with powershell commands.

---

Short version (package first approach in Powershell)

• For an examplanation on what each command does, please refer to the "long version"

1. Prerequisites (somewhere with a restart when the command line says so):
   1. dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart
   2. dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
   3. wsl --install
   4. wsl --update
2. winget.exe install --id Docker.DockerCLI
3. winget.exe install --id RedHat.Podman
4. winget.exe install --id RedHat.Podman-Desktop (optional, but nice to have UI)
5. podman machine init
6. wsl sudo sysctl net.ipv4.ip_forward=1

Testing

• docker run --rm -d -p 8080:80 --name httpd docker.io/library/httpd
• open localhost:8080 in your browser

---

Docker CLI with Podman Daemon

a.k.a UI First Approach (or rather the "problems first" approach)

Steps Guide

This guide is based on a freshly reset Win 11 install, that is akin to a new installation too. Thus, it is based on the exact steps I made, based on the problems I have encountered to have a fully functioning setup.

Step 1. Download Podman Desktop

Sources:

• Podman website
• Podman WingeUi Package

Step 2. Install Podman Desktop

• 2.1 Run the normal installation until you get to the landing page such as below:
  

Step 3. Configure Podman Client and WSL features

• 3.1 Press "Go to Podman Desktop"

• 3.2 on the next page you should see:
  

• 3.3 On this page you should press the "Install" button

  • 3.3.1 the following error might occur:
    
    • this error means that the Virtual Machine Platform feature has not yet been enabled
    • Solution: https://learn.microsoft.com/en-us/windows/wsl/install-manual#step-3---enable-virtual-machine-feature
    • Run the following command in Powershell: dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

• 3.4 After enabling the VM Platform Feature, you might encounter this error:
  

  • 3.4.1 This problem means that there are no installed "Windows Subsystem for Linux" versions installed

    • furthermore, this error might be paired with these messages (during the regular setup process //see point 3.2 and choosing "Setup")
      
      

  • 3.4.2 At this point, you might also receive an error from Powershell for wsl --install command:

    > -Class not registered
    Error code: Wsl/CallMsi/REGDB_E_CLASSNOTREG
    
    - this means that you don't have the WSL feature enable at all
         - **Solution**:
             - Run this command: `dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart`
             - 
    

• 3.5 Now you can use the wsl --install command for Powershell

  • 3.5.1 also, don't forget to use wsl --update thereafter, to make sure you have the latest updates for WSL

• 3.6 Check the requirements again, if all goes well you should be greeted with:
  

  • This means, that the Podman Client is not installed
  • Proceed with the installation (press "Yes"), you'll be greeted with:
    
  • Proceed with the defaults and press "Install"

Step 4 Setup Podman Machine

• Podman machine is the daemon that is running in WSL, that we can communicate with in order to launch containers

• 4.1 Inside Podman Desktop GUI, Navigate to Settings(Cog-icon, button left)/Resources

  • 4.1.1 As you don't have any podman machines yet you'll be greeted with:
    
    

• Proceed with the defaults
  

• 4.2 at this point you might encounter:
  

  • For me, this was caused because the installer didn't actually manage to install WSL's optional components
    • Debug steps included trying to init from GUI, which produced the same error.
  • Solution:
    • In PowerShell, running the command "podman machine init"
      • windows prompts for:
        
    • proceeding with the install will produce the following:
      
    • At this point you should restart your machine

• 4.3 at this point you should be able to:

  • start a podman machine successfully with Powershell command: podman machine init (inits default machine)
  • start / stop the podman machine with Powershell command: podman machine start / podman machine stop

Step 5 Install Docker.Cli

• 5.1 Install Package: https://marticliment.com/wingetui/share?pid=docker-cli&pname=Docker Cli&psource=Chocolatey

• 5.2 Make sure that Powershell answers correctly for command: docker info

• 5.3 If at the end of docker info you see:
  

• This means that you have to open enable IPv4 port forwarding

• Solution:

  • Open Powershell and use command: wsl (opens the installed WSL system's console)
  • Use command: sudo sysctl net.ipv4.ip_forward=1 (enbles IPv4 port forwarding)
  • You can exit the WSL console by typing exit (might need to type it twice to get back to Powershell)
  • Make sure docker info doesn't have the aforementioned error anymore

DONE

• at this point you should be able to pull images in Powershell, using the docker keyword
  • example:
    • by running docker run --rm -d -p 8080:80 --name httpd docker.io/library/httpd
      • you should be able to see the running container in Podman Desktop's GUI
      • as well as get the text response "Ok" when connecting to localhost:8080, confirming that the container is running
• furthermore, in Visual Studio IDE, you should have a fully functioning "View/Containers" tab
  • if you have tried to run a solution that is supposed to have a container publish before
  • you might encounter a popup saying "docker.exe" cannot be found
  • however, after closing that window the solution should run as intended
  • this problem was no longer happening on a freshly installed VS IDE, and a freshly cloned Solution, so it can be possible a simple deletion of VS specific files in the solution folder, might solve the popup (otherwise it's a WIP to find out where VS actually gets the idea from, wrongly)

[GarretWayne]

@tlunsfordCXP

I dropped my guide that I did a while back. I hope this can help the rabbit hole problem ;)

It has been stable for me since then and this is my current setup.

[Ungerfall]

I followed the guide, but on docker run --rm -d -p 8080:80 --name httpd docker.io/library/httpd getting

docker: no matching manifest for windows/amd64 10.0.22631 in the manifest list entries.

Was it because I didn't remove Docker Desktop correctly? Or should I follow @soerennielsen instruction to create a symb link?

[jrlost]

Are/were you running windows containers?

…

On Mon, Jan 20, 2025, 5:37 AM Leonid ***@***.***> wrote: I followed the guide, but on docker run --rm -d -p 8080:80 --name httpd docker.io/library/httpd getting docker: no matching manifest for windows/amd64 10.0.22631 in the manifest list entries. Was it because I didn't remove Docker Desktop correctly? Or should I follow @soerennielsen <https://github.com/soerennielsen> instruction to create a symb link? — Reply to this email directly, view it on GitHub <#17131 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAVCEN5XDDGMNPSMG777JED2LTNWXAVCNFSM6AAAAABVQFEXVWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBYHE3DAMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[soerennielsen]

I didn't.

[Ungerfall]

After I installed the docker cli via winget The docker info gave

OSType: windows

Then I tried to find how to change the OSType, and it seemed impossible without Docker Desktop.
Now I checked after the restart

OSType: linux

[soerennielsen]

? but the OSType depends on the docker/podman host.
For both I would use WSL which in turn mean that it is linux containers.

You are gonna hit compatibilty issues when you have both installed. You can but make sure that one is only used at any one time as they will fight over the named pipes otherwise.

It has been a few years since I dabled in windows containers, but it is using hyper-v, not wsl to do that. Worked okish with docker, never trided with podman - I suspect it is not supported.