本地Jenkins流水线中运行Docker容器失败，是否需改用容器化Jenkins？

Got it, let's fix this issue for you. The error message you're seeing is because your local Jenkins instance isn't running inside a Docker container itself—so it can't properly spin up and manage Docker containers for the pipeline agent. Here's a straightforward solution to get your pipeline working:

1. Why This Error Occurs #

When you use agent { dockerfile true } in your Jenkinsfile, Jenkins needs direct access to the Docker daemon to build and run the container defined in your Dockerfile. If Jenkins is installed directly on your host machine (not in a container), it lacks the proper permissions and context to interact with Docker seamlessly. Running Jenkins inside a container is the standard approach to resolve this.

2. Run Jenkins as a Docker Container #

First, stop your existing local Jenkins service if it's running. Then follow these steps:

• Create a local directory to persist Jenkins data (so you don't lose settings when the container restarts):

  mkdir -p ~/jenkins_data
  

• Launch the containerized Jenkins instance, mounting the necessary volumes to access Docker and save data:

  docker run -d \
    -p 8080:8080 \
    -p 50000:50000 \
    -v ~/jenkins_data:/var/jenkins_home \
    -v /var/run/docker.sock:/var/run/docker.sock \
    jenkins/jenkins:lts
  

  Let's break down these flags:
  • -d: Runs the container in the background
  • -p: Maps host ports to container ports (8080 for the Jenkins web UI, 50000 for agent communication)
  • -v ~/jenkins_data:/var/jenkins_home: Persists Jenkins configuration and jobs to your host
  • -v /var/run/docker.sock:/var/run/docker.sock: Gives the Jenkins container access to your host's Docker daemon

3. Fix a Typo in Your Environment Variable #

Quick note: I spotted a typo in your files that will cause the env var to not print correctly. Your Dockerfile defines customnEnvVar (extra 'n'), but your Jenkinsfile references customEnvVar. Fix the Dockerfile to match:

FROM ubuntu
ENV customEnvVar="test."

Your Jenkinsfile can stay mostly the same—adding a stage name makes it clearer:

#!groovy
pipeline {
    agent { dockerfile true }
    stages {
        stage('Print Environment Variable') {
            steps {
                sh 'echo customEnvVar = $customEnvVar'
            }
        }
    }
}

4. Troubleshooting Permissions #

If you still run into Docker permission errors after setting up the container:

1. Get your Jenkins container ID: docker ps
2. Enter the container shell:

   docker exec -it <your-jenkins-container-id> /bin/bash
   

3. Add the jenkins user to the Docker group:

   usermod -aG docker jenkins
   

4. Restart the Jenkins container: docker restart <your-jenkins-container-id>

内容的提问来源于stack exchange，提问作者m aksem