jenkins'执行脚本'构建步骤错误：/ bin/docker：权限被拒绝

Question

我试图在我的个人电脑上构建一个简单的管道。我有詹金斯ver。 2.32.2安装并运行。下面是我的流水线作业DSL：

node { 
    stage('Github Checkout') { 
     checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[credentialsId: '921fd840-1d71-4b06-bf5e-1c6f3141f669', url: 'git@github.com:justinsr20/tdd_django.git']]]) 
    } 
    stage('Build containter image') { 
     sh 'whoami' 
    } 
     stage('Build containter image') { 
     sh 'pwd' 
    } 
    stage('Build containter image') { 
     sh 'ls -l' 
    } 

    stage('Build containter image') { 
     sh 'docker build -t jenkins/django:v1 -t jenkins/django:latest .' 
    } 
} 

我已经安装了码头工人和我有泊坞窗组中的詹金斯用户：

[root@localhost bin]# grep 'docker' /etc/group 
docker:x:977:judd,jenkins 

奇怪的是，詹金斯给我下面的权限错误试图在我上面定义管道运行的泊坞窗构建命令时：

[workspace] Running shell script 
+ whoami 
jenkins 
[Pipeline] } 
[Pipeline] // stage 
[Pipeline] stage 
[Pipeline] { (Build containter image) 
[Pipeline] sh 
[workspace] Running shell script 
+ pwd 
/var/lib/jenkins/jobs/tdd_django/workspace 
[Pipeline] } 
[Pipeline] // stage 
[Pipeline] stage 
[Pipeline] { (Build containter image) 
[Pipeline] sh 
[workspace] Running shell script 
+ ls -l 
total 20 
drwxr-xr-x. 3 jenkins jenkins 4096 Feb 10 11:11 django_app 
-rw-r--r--. 1 jenkins jenkins 97 Feb 10 12:37 Dockerfile 
-rw-r--r--. 1 jenkins jenkins 15 Feb 10 11:11 requirements.txt 
-rw-r--r--. 1 jenkins jenkins 66 Feb 10 11:11 run_tests.sh 
-rwxr-xr-x. 1 jenkins jenkins 69 Feb 10 12:48 script.sh 
[Pipeline] } 
[Pipeline] // stage 
[Pipeline] stage 
[Pipeline] { (Build containter image) 
[Pipeline] sh 
[workspace] Running shell script 
+ docker build -t jenkins/django:v1 -t jenkins/django:latest . 
/var/lib/jenkins/jobs/tdd_django/workspace@tmp/durable-77854956/script.sh: line 2: /bin/docker: Permission denied 

我的搬运工权限：

bash-4.3$ which docker 
/bin/docker 
bash-4.3$ ls -la /bin/docker 
-rwxr-xr-x. 1 root root 12056512 Feb 8 16:44 /bin/docker 

但是当我打开一个shell会话中，詹金斯用户，我可以运行该命令没有问题：

[root@localhost bin]# sudo su -s /bin/bash jenkins 
bash-4.3$ cd /var/lib/jenkins/jobs/tdd_django/workspace 
bash-4.3$ ls 
django_app Dockerfile requirements.txt run_tests.sh script.sh 
bash-4.3$ docker build -t jenkins/django:v1 -t jenkins/django:latest . 
Sending build context to Docker daemon 76.8 kB 
Step 1/3 : FROM python:2.7-onbuild 
# Executing 3 build triggers... 
Step 1/1 : COPY requirements.txt /usr/src/app/ 
---> Using cache 
Step 1/1 : RUN pip install --no-cache-dir -r requirements.txt 
---> Using cache 
Step 1/1 : COPY . /usr/src/app 
---> Using cache 
---> fb9aa7078336 
Step 2/3 : LABEL maintainer "CMI Industries" 
---> Using cache 
---> c1888038ffa2 
Step 3/3 : RUN chmod +x /usr/src/app/run_tests.sh 
---> Using cache 
---> 8e61860e0567 
Successfully built 8e61860e0567 

任何帮助，将不胜感激。

编辑更新：

所以如果issues.jenkins-ci.org/browse/JENKINS-24338是与我需要修改泊坞窗如何启动服务。

systemctl start docker 

找到这个命令我使用的配置文件：

[root@localhost system]# systemctl show --property=FragmentPath docker 
FragmentPath=/usr/lib/systemd/system/docker.service 

这个文件的内容：我从开始我的搬运工服务

[Unit] 
Description=Docker Application Container Engine 
Documentation=https://docs.docker.com 
After=network.target firewalld.service 

[Service] 
Type=notify 
# the default is not to use systemd for cgroups because the delegate issues still 
# exists and systemd currently does not support the cgroup feature set required 
# for containers run by docker 
ExecStart=/usr/bin/dockerd 
ExecReload=/bin/kill -s HUP $MAINPID 
# Having non-zero Limit*s causes performance problems due to accounting overhead 
# in the kernel. We recommend using cgroups to do container-local accounting. 
LimitNOFILE=infinity 
LimitNPROC=infinity 
LimitCORE=infinity 
# Uncomment TasksMax if your systemd version supports it. 
# Only systemd 226 and above support this version. 
#TasksMax=infinity 
TimeoutStartSec=0 
# set delegate yes so that systemd does not reset the cgroups of docker containers 
Delegate=yes 
# kill only the docker process, not all processes in the cgroup 
KillMode=process 

[Install] 
WantedBy=multi-user.target 

林不知道如何我需要修改这个文件，这样我就可以“配置docker服务来将'jenkins'组的所有权应用到套接字上，而不是将jenkins用户添加到默认使用的'docker'组中”，如issue.jenkins-ci.org/中所解释的那样。浏览/ JE NKINS-24338

Answer 1

好像你遇到了selinux。运行命令sestatus会让你知道它是什么模式，在你的情况，这将是enforcing

为了获得什么规则，你了解更多信息需要添加，使SELinux的快乐，我会建议你设置了SELinux通过编辑此文件到permissive：/etc/sysconfig/selinux然后重新启动。我相信还有一种方法可以在不重启的情况下更改模式（尽管它不是永久性的）。

一旦selinux处于permissive模式（它只会记录并不会阻塞），您可以在运行jenkins作业时尾部登录/var/log/audit/audit.log。这应该让你知道它需要什么权限。