Podman 4.2.0 • Hacker News Board

Re: Podman 4.2.0

#101

Post by pxc » Fri, Aug 12, 2022, 4:53 AM UTC

emptysongglass wrote: post #95

pxc wrote: post #81

Earlier quoted context omitted.

If you install the podman package via Scoop, you'll get a `podman` client shim, and then if you run `podman machine init` it'll automatically set up a WSL instance running Fedora with Podman set up and relay the necessary sockets for you so that running `podman ps` or whatever on Windows Just Works™. Then if you want to can run `wsl -d podman-machine-default` to log into the distro as normal. You can also copy the di…

What the official Windows Podman installer, also official Podman Desktop that installs Podman and scoop's Podman package should really do is offer to integrate with your existing WSL2 distro like Docker Desktop does.

The way that Docker Desktop integrates is just one extra step away from `podman machine init`, since Docker Desktop just does the same socket relaying stuff for your existing WSL distros as it does for Windows. The actual Docker daemon only runs on the special distro that the tool (Docker Desktop or `podman machine` or whatever) sets up.

I assume that Podman Desktop does that but idk because I don't use it. Rancher Desktop also works this same way.

In all cases, the integration with existing distros happens inside the GUI app. Maybe I'll check tomorrow whether Podman Desktop offers comparable integration.

But yeah, it's a good integration to have because the native Windows CLI experience is still so impractical and clunky that many developers end up setting up a pet distro in WSL and pretty much living in it as their default terminal session. Good integration with cmd.exe or (pwsh.exe running under Windows Terminal, for that matter) is cool but it doesn't mean much to someone who does all their work in an Ubuntu WSL VM or whatever.

Re: Podman 4.2.0

#102

Post by jacooper » Sat, Aug 13, 2022, 11:56 AM UTC

eriksjolund wrote: post #63

jacooper wrote: post #61

Earlier quoted context omitted.

> - Faster network. Rootless Podman will run with native network speed. Normally rootless Podman runs with reduced network speed due to the performance penalty that comes from using slirp4netns. Did they fix the IP propagation issue with Rootless networking ? It makes it largely useless when the Proxy is also a container. on Docker you can force it to use Slirp, but its slow and doesn't support IPv6.

You could detect the source IP address by using the command-line option: --net=slirp4netns:port_handler=slirp4netns See https://github.com/containers/podman/discussions/10472#discu... Shouldn't it also be possible to detect the source IP address if you use socket activation? (I haven't tried it out, though).

But that's using Slirp, which has its own problems.

Re: Podman 4.2.0

#103

Post by eriksjolund » Sun, Aug 14, 2022, 8:57 AM UTC

eriksjolund wrote: post #57

bongobingo1 wrote: post #8

Big fan of Podman. Technically every time I have tried to push it into my production workflow I've hit some snags, mostly around networking and some volume stuff but those snags are getting chipped away each release. The last time I did a strong test flight was around 3.X, so probably about time to try again, 4.0 was a big release. I like the integration with systemd and bringing "pods" out of k8. I like the "they're…

I haven't tried it out, but shouldn't you be able to detect the true remote address by using a socket that has been passed in via socket activation?

The remote address is available when running a socket-activated container with rootless Podman. I verified it in a test.

Re: Podman 4.2.0

#104

Post by eriksjolund » Sun, Aug 14, 2022, 9:03 AM UTC

jacooper wrote: post #102

eriksjolund wrote: post #63

Earlier quoted context omitted.

You could detect the source IP address by using the command-line option: --net=slirp4netns:port_handler=slirp4netns See https://github.com/containers/podman/discussions/10472#discu... Shouldn't it also be possible to detect the source IP address if you use socket activation? (I haven't tried it out, though).

But that's using Slirp, which has its own problems.

Ok, I understand your concern about Slirp.

Regarding the other idea: I've now tested it and verified that it works. The remote address is available when running a socket-activated container with rootless Podman.