image
这两天在玩jenkins，但是在挂在数据卷的时候遇到了权限问题，如下，
docker启动命令
docker run -d -v /root/jenkins:/var/jenkins_home -P --name jenkins-server jenkins
这个命令看似没有什么问题，但容器就是启动不起来，执行docker ps -a，查看container,如下，
[root@esslog-shqs-6 ~]# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
274d92964edb jenkins "/bin/tini -- /usr/lo" 2 minutes ago Exited (1) 2 minutes ago jenkins-server
接着执行docker logs jenkins-server查看container日志，如下
Can not write to /var/jenkins_home/copy_reference_file.log. Wrong volume permissions?
touch: cannot touch ‘/var/jenkins_home/copy_reference_file.log’: Permission denied
日志中出现了一个Permission denied错误，，以我目前的功力还不清楚是什么问题造成的，但是在谈谈Docker Volume 之权限管理和持续集成（Continuous integration）两篇博客中找到了答案，在执行docker run命令的时候增加一个-u参数，如下改进后的命令，
docker run -d -v /root/jenkins:/var/jenkins_home -u 0 -P --name jenkins-server jenkins
这命令的意思是覆盖容器中内置的帐号，该用外部传入，这里传入0代表的是root帐号Id。这样再启动的时候就应该没问题了。
如果按照上面做还是出现Permission denied错误，那么可以检查一下selinux状态，开启的情况下会导致一些服务安装、使用不成功。
查看selinux状态，
[root@localhost ~]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 28
临时关闭，
[root@localhost ~]# setenforce 0
永久关闭,可以修改配置文件/etc/selinux/config,将其中SELINUX设置为disabled，如下，
[root@localhost ~]# cat /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
#SELINUX=enforcing
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
[root@rdo ~]# sestatus
SELinux status: disabled
相关：
docker registry push错误“server gave HTTP response to HTTPS client”
参考文章：
http://www.cnblogs.com/99fu/p/6042744.html
https://yq.aliyun.com/articles/53990
http://blog.csdn.net/one_clouder/article/details/39224767
http://www.orcs.cc/post/6.html
