commit d1c7393332e755eb5414a45431da5031e354e7df
parent c86e36fa0a0b6e7273dbd5bb373a15a2f5ae3697
Author: Andreas Gruhler <agruhl@gmx.ch>
Date: Sat, 3 May 2025 22:42:37 +0200
doc(jenkins-inbound-agent): podman socket lingering
Diffstat:
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docker/docker-jenkins-inbound-agent/README b/docker/docker-jenkins-inbound-agent/README
@@ -69,7 +69,8 @@ Note:
inbound agent with the same UID/GID that are used by Nomad to spawn the
Jenkins agent job.
* The Docker socket shared with the Nomad job (the Jenkins agent) here needs to
- be activated and run in the background (see enable-linger below)
+ be activated and run in the background (see
+ https://code.in0rdr.ch/hashipi/file/nomad.sh.html)
Because the Jenkins agent sits in between our Podman host (the Nomad agent) and
the downstream Docker container where we run our app logic, it is essential to
