Support podman as container runtime by upgrading debian container image

[ericzolf]

issue

when trying to start the containers front, pusher, back, uploader, messages as described in docker-compose.single-domain.yaml using podman, they fail all with exactly the same logs message:

sudo: unable to send audit message
sudo: pam_open_session: System error
sudo: policy plugin failed session initialization

There is probably one unique thing to fix to make it work under podman, which would simplify development on Fedora, CentOS and RHEL.

reproduce

There are multiple ways but here is mine under Fedora 35:

1. install ansible-core and podman
2. install containers.podman collection (ansible-galaxy collection install containers.podman)
3. start in a separate console sudo podman system service --time=0
4. source .env.template
5. run ansible-playbook -K workadventure.single-domain.up.yml using
   workadventure.single-domain.up.yml placed in the root directory of the workadventure Git repo
6. sudo podman ps -a resp sudo podman logs front (for example) show the issue described above

comments

• I've generated the playbook using https://github.com/ericzolf/doco2podans
• the setup can be removed with
  workadventure.single-domain.down.yml

[ericzolf]

I saw the comment about (allowPrivilegeEscalation under Kubernetes](https://hub.docker.com/r/thecodingmachine/nodejs), but it's not the same error message, and other images don't have an issue with sudo without special parameter (which I wouldn't know the equivalent for podman). For example docker.io/thecodingmachine/php:8.1-v4-apache-node12 doesn't show the issue, a sudo is possible without issue.

The main difference I see betwen both images is that the failing one uses debian-slim where the other uses ubuntu, but that doesn't tell me how to fix the issue.

[ericzolf]

I can reproduce the issue with the base image:

$ sudo podman run -it --rm debian:stretch-slim
# apt update
# apt install sudo
# sudo -i

[ericzolf]

The above steps succeed on debian:bullseye-slim so the solution might be as "simple" as bumping the base image version everywhere.

[lukashass]

Have you seen thecodingmachine/docker-images-nodejs#14?

On another note: As far as I can see it would be possible to replace most of the development images (except maps) with official node images.