From 5528363904dcedbd3e447b91878fc75e7febabf0 Mon Sep 17 00:00:00 2001 From: chrysn Date: Fri, 21 Jul 2023 10:08:25 +0000 Subject: [PATCH] Add guidance for using podman with the runner --- admin/actions.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/admin/actions.md b/admin/actions.md index e4ad5fde..9618ee08 100644 --- a/admin/actions.md +++ b/admin/actions.md @@ -60,6 +60,22 @@ Good signature from "Forgejo " For jobs to run in containers, the `Forgejo runner` needs access to [Docker](https://docs.docker.com/engine/install/). +### Podman + +While Podman is generally compatible to Docker, +it does not run socket for managing containers by default +(because it doesn't usually need one). + +If the Forgejo runner complains about "daemon Docker Engine socket not found", or "cannot ping the docker daemon", +you can use podman to provide a Docker compatible socket from an unprivileged user +and pass that socket on to the runner, +e.g. by executing: + +```shell +$ podman system service -t 0 & +$ DOCKER_HOST=unix://${XDG_RUNTIME_DIR}/podman/podman.sock ./forgejo-runner daemon +``` + ### LXC For jobs to run in LXC containers, the `Forgejo runner` needs passwordless sudo access for all `lxc-*` commands on a Debian GNU/Linux `bookworm` system where [LXC](https://linuxcontainers.org/lxc/) is installed. The [LXC helpers](https://code.forgejo.org/forgejo/lxc-helpers/) can be used as follows to create a suitable container: