About Podman - issue #303

[metal3d]

The issue #303 is actually paused but I managed to use Podman on my computer.

I will probably create an article but it's pretty simple (on Fedora at least).

Podman is rootless, so let's take advantage of that!

1 - activate the "podman.socket" for the user:

systemctl --user enabled --now podman.socket
systemctl --user status podman.socket

## output

● podman.socket - Podman API Socket
     Loaded: loaded (/usr/lib/systemd/user/podman.socket; enabled; preset: disabled)
     Active: active (running) since Sun 2025-07-13 22:19:30 CEST; 2 days ago
 Invocation: 233ae0ef0a5e42a0958667c3bbefb8b7
   Triggers: ● podman.service
       Docs: man:podman-system-service(1)
     Listen: /run/user/1000/podman/podman.sock (Stream)
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/podman.socket

juil. 13 22:19:30 patrice-laptop systemd[2179]: Listening on podman.socket - Podman API Socket.

The socket should now be accessible with /run/$(id -u)/podman/podman.socket

2- use act with this socket:

act --container-daemon-socket=/run/user/1000/podman/podman.sock
# or
# act --container-daemon-socket)=${XDG_RUNTIME_DIR}/podman/podman.sock

You can set DOCKER_HOST environment too :) see https://nektosact.com/usage/custom_engine.html

[Demo/test] ⭐ Run Main go test -v .
[Demo/test]   🐳  docker exec cmd=[sh -e /var/run/act/workflow/2.sh] user= workdir=
| === RUN   TestAdd
| === RUN   TestAdd/ok
| === RUN   TestAdd/ok#01
| === RUN   TestAdd/should_fail
| --- PASS: TestAdd (0.00s)
|     --- PASS: TestAdd/ok (0.00s)
|     --- PASS: TestAdd/ok#01 (0.00s)
|     --- PASS: TestAdd/should_fail (0.00s)
| PASS
| ok    example 0.002s
[Demo/test]   ✅  Success - Main go test -v . [4.744309157s]
[Demo/test] ⭐ Run Complete job
[Demo/test] Cleaning up container for job test
[Demo/test]   ✅  Success - Complete job
[Demo/test] 🏁  Job succeeded

That's all. I'm pretty sur we can set the value in a config file, I didn't checked.