modulesync 10.5.0

[pccibot]

modulesync 10.4.0

[traylenator]

Relevant change - voxpupuli/gha-puppet#82

Now running on container_podman rather than docker.

[traylenator]

podman run   --tmpfs /run --tmpfs /run/lock --cap-add=SYS_ADMIN  --security-opt seccomp=unconfined --security-opt label=disable  --userns=host debian:13 /bin/bash -c   "apt update ; apt install -y  autofs ; /usr/sbin/automount"

fails with the same error

/usr/sbin/automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required.

where as

podman run  --privileged debian:13 /bin/bash -c   "apt update ; apt install -y  autofs ; /usr/sbin/automount"

works. This somewhat implies that we are not running podman with --privileged ...

[traylenator]

Understood probably:

  bundle exec rake beaker
  shell: /usr/bin/bash -e {0}
  env:
    BEAKER_HYPERVISOR: container_podman
    BUNDLE_WITHOUT: development:test:release
    BEAKER_HCLOUD_TOKEN: 
    DOCKER_HOST: unix:///run/user/1001/podman/podman.sock

So with that DOCKER_HOST we are running rootless podman - that is doomed even with --priviledged.

• Either get access to the system podman socket or
• Change the tests use the mount_method => mount and forget about autofs.

[TheMeier]

I was chasing that in the autofs module,if you do podman inspect it reports that privilieged mode and subsequentailly a nearly all capabilities are enabled.
So you are saying both are irrelevant due to DOCKER_HOST being set? Why is it set in the first place, is that actually a thing from using docker in the past?

[traylenator]

We are running both docker and podman as a user.
In this case docker still defaults to the root owned socket where as a podman defaults to the user owned socket... So in reality we probably do not need to set it for either case. Not setting it will change nothing however.

I've got a MR on gha-puppet to use the root owned socket with podman however while it works on my laptop it is not in CI :-( See the MR.

Even if it did work it's a bit dirty. Think solution is to switch to vagrant hypervisor for this and autofs, have not got around to trying yet.