Upgrade to Podman 3.2.1

[MarkusSchoelzel]

Update PODMAN_VERSION, LIBSLIRP_VERSION and SLIRP4NETNS_VERSION

Revert seccomp fixes as they are not needed anymore

[mgoltzsche]

Awesome! Thanks @MarkusSchoelzel!

However the podman remote test fails:

$ docker run --rm --network=host -v /home/runner/work/podman-static/podman-static/test:/build mgoltzsche/podman:latest-remote podman --url=tcp://127.0.0.1:53453 run alpine:3.13 echo hello from remote container
Error: error preparing container 77377036ac30d9c71ffe8184a3e50c29fb98c000041b5a97360765e0278d4ad1 for attach: error creating resolv.conf for container 77377036ac30d9c71ffe8184a3e50c29fb98c000041b5a97360765e0278d4ad1: detected that systemd-resolved is in use, but could not locate real resolv.conf: open /run/systemd/resolve/resolv.conf: no such file or directory

Would you mind also bumping the version within the podman-remote Dockerfile Dockerfile-remote here?

Maybe that also fixes the issue in the test. It looks like a podman bug though since systemd is not supported within the container podman is run in but on the host. Maybe the configuration or the test needs to be tweaked a bit to make it work. I ll look into it a bit more the next days. In case you're looking at this earlier and create a podman issue please link it here.

...On second thought: podman probably detects systemd because this test runs it within a container within the host network - this is likely the reason for the failure since the other tests succeed and don't run within the host network. I think the test could be disabled for now in order to get this PR merged and a podman issue created in case there is none for it already.

[mgoltzsche]

I verified that this is a podman bug (using a build from this PR):

The following works fine:

$ docker run --rm --privileged -u podman:podman mgoltzsche/podman:latest podman run alpine:3.13 echo hello world
...
hello world

However if I do the same using the host network podman fails:

$ docker run --network=host --rm --privileged -u podman:podman mgoltzsche/podman:latest podman run alpine:3.13 echo hello world
...
Error: error creating resolv.conf for container 54ac262cd322f9e70ecfdd3ce2bb72ba97ed1a9f654e05c86a7b1710a02e1fb6: detected that systemd-resolved is in use, but could not locate real resolv.conf: open /run/systemd/resolve/resolv.conf: no such file or directory

Apparently this is caused by containers/podman#10598.

Therefore I'll merge your PR now, bump the podman-remote version as well, disable the remote test, create a new release in this repo and create a podman issue/PR to fix the bug...