Jenkins构建Docker镜像失败求助：直接运行Dockerfile正常但Jenkins执行报错

Hey, I've run into similar permission headaches when using Jenkins to build Docker images before—let's break down the possible causes and fixes for your case:

1. Jenkins工作目录权限不足 #

The most common culprit here is that the Jenkins user (usually jenkins) doesn't have proper read/write/execute permissions on your build context directory. When you run docker build locally, you're probably using your own account with full access, but Jenkins runs under a restricted user that can't interact with the build files properly.

Fix:

• First, check the permissions of your Jenkins workspace directory:

  ls -ld /var/lib/jenkins/workspace/your-project-dir
  

• If the owner isn't the jenkins user, fix it with:

  sudo chown -R jenkins:jenkins /var/lib/jenkins/workspace/your-project-dir
  

• Alternatively, add a pre-build step in Jenkins to temporarily loosen permissions (great for testing, adjust for production):

  chmod -R 755 .
  

2. 安全模块（AppArmor/SELinux）干扰容器操作 #

If your Jenkins server has AppArmor or SELinux enabled, these security tools might block the container from accessing its working directory during the pecl install step. Local builds often don't have these restrictions enabled, which is why they succeed.

Fix:

• For testing, disable AppArmor for the container by adding this flag to your docker build command in Jenkins:

  docker build --security-opt apparmor:unconfined -t your-image .
  

• For SELinux, either add a security flag or adjust the directory's SELinux context:

  # Option 1: Disable label enforcement temporarily
  docker build --security-opt label:disable -t your-image .
  
  # Option 2: Set correct SELinux context for the build directory
  chcon -Rt svirt_sandbox_file_t /var/lib/jenkins/workspace/your-project-dir
  

Note: Re-enable these security measures in production once you confirm they're the root cause.

3. 强制切换到容器内有权限的目录 #

The error ls: cannot access '.': Operation not permitted tells us the container's current working directory lacks access rights. You can work around this by switching to /tmp (a universally writable directory) before running the pecl install command.

Fix:
Modify your Dockerfile step to:

RUN cd /tmp && pecl install xdebug-3.0.4 && docker-php-ext-enable xdebug

4. 清理Docker缓存 #

Stale cached layers from previous builds can cause permission inconsistencies. Your local build might be using cached layers that avoid the issue, while Jenkins is building from scratch and hitting the permission block.

Fix:
Add the --no-cache flag to your docker build command in Jenkins to force a fresh build:

docker build --no-cache -t your-image .

内容的提问来源于stack exchange，提问作者Mohamed Salem