nomad

commit c05ac4c4894b34fc9569625518a76072e5b25e6d
parent bcc4cf303eede08485d6766d5eba9737be3c896c
Author: Andreas Gruhler <andreas.gruhler@adfinis.com>
Date:   Sun,  7 Jul 2024 12:22:42 +0200

doc(jenkins-agent): update readme

Diffstat:
M
docker/docker-jenkins-inbound-agent/README
 | 
20
+++-----------------

1 file changed, 3 insertions(+), 17 deletions(-)
diff --git a/docker/docker-jenkins-inbound-agent/README b/docker/docker-jenkins-inbound-agent/README
@@ -108,7 +108,7 @@ needs to be mounted to each Jenkins agent.
  +------------+
 
 The Docker pipeline (docker-workflow) plugin has the default configuration to
-automatically mound a Docker volume in `/home/jenkins/workspace`.
+automatically mount a Docker volume in `/home/jenkins/workspace`.
 
 This can be seen in the log of Jenkins when the first Job with a docker
 pipeline configuration starts:
@@ -189,8 +189,7 @@ Nomad:
 
 == Jenkins Pipeline examples ==
 
-The pipeline examples need to ensure that the user (`-u` flag) is set to the
-user of the Docker image. Two "declarative" pipeline examples:
+Two "declarative" pipeline examples:
 
  pipeline {
      agent {
@@ -198,8 +197,6 @@ user of the Docker image. Two "declarative" pipeline examples:
            image 'docker.io/arm64v8/alpine:latest'
            // The Nomad cloud spawns Nomad agents with that label
            label 'podman'
-           // User needs to match the user in the container, otherwise you
-           // encounter errors while accessing "durable" directories.
            args '-u root'
          }
      }
@@ -236,8 +233,7 @@ user of the Docker image. Two "declarative" pipeline examples:
 The "scripted" pipeline is similar:
 * https://www.jenkins.io/doc/book/pipeline/docker
 
-Makes sure to set the label of the node ("podman") and the proper user for the
-Docker container (-u flag). Few examples:
+Makes sure to set the label of the node ("podman"). Few examples:
 
  node('podman') {
      stage('runInDocker') {
@@ -277,16 +273,6 @@ Docker container (-u flag). Few examples:
 Even more examples (not necessarily docker related):
 * https://www.jenkins.io/doc/pipeline/examples
 
-== Note on Docker images ==
-
-Some images (such as debian:stable-slim) don't have the `top` command. This
-will return an error when run in Jenkins:
-
-"java.io.IOException: Failed to run top"
-
-In this case, build an image based on the desired image that includes top
-(procps).
-
 == Integration with Git post-receive hooks ==
 
 There exists the option to nudge Jenkins on every push, see