Hacker News Reader

Comment by no_carrier | Hacker News Reader

You absolutely can run docker on the CLI in WSL2. The only requirement is you have systemd running in your WSL distro, which is fully supported.

View on HN

Yes, of course that works, but then you have to start up and shell into WSL. With podman, you can run all commands directly in Windows which is more seamless. Plus, getting it working is just a matter of running "winget install -e --id RedHat.Podman". This is particularly helpful when trying to roll things out for larger teams as they don't have to know anything about WSL and everything integrates in their environment seamlessly. Of course, just using Linux is preferable for development if you can get away with it.

> You absolutely can run docker on the CLI in WSL2.

But again, they're talking about Windows, not Linux-in-Windows or virtualized Linux on Windows. Just because you can do something in WSL2 doesn't mean you "can do it on Windows", as much as you "can run systemd and Wayland on Windows" because you could run it inside a Linux VM...

Yes. For some the distinction between the two is almost nothing as WSL is pretty seamless. However, using Podman directly in your normal Windows shell opens up more use cases. Podman is of course running everything behind the scenes using WSL.

> For some the distinction between the two is almost nothing as WSL is pretty seamless

WSL1 yes, but not WSL2, which the parent explicitly mentioned. WSL2 is just virtualization with a fancier name, might as well use VirtualBox and similar at that point.

While it is fundamentally a VM, it is far more seamless than running a regular VirtualBox.

Your posts in this thread seem to be focused on the inability to use Docker from the Windows shell, but it's not true: you just need to set DOCKER_HOST. Then the Windows client can connect to a Linux engine in WSL2. Docker engine in WSL2 runs as a systemd unit and doesn't need to be manually started. Podman/Docker Desktop are doing far less work here than you might be expecting. They are just automating this setup for you. I run this setup and it is genuinely a one-time nothingburger. If you have a bunch of Windows machines, you can have them all share one Linux Docker engine if you want, by pointing DOCKER_HOST at the same host.

Reply on news.ycombinator.com