[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

[golube...@gmail.com (JIRA)]

Valeri Golubev edited a comment on JENKINS-24338 Issues with docker permissions I had the same issue, as described earlier, that docker container was successfully running under 'su - jenkins' but failed when executing by script build step. Versions: jenkins: 1.555 os: CentOS release 6.6 (Final) docker: Docker version 1.3.2, build 39fa2fa/1.3.2 I found a work-around, that probably can be helpful to further clarify the issue. In order to allow jenkins to create and manage docker containers via 'execute script' build step, you can configure docker service to apply 'jenkins' group ownership to the socket, rather than adding jenkins user to the default-used 'docker' group. This configuration can be achieved by adding the '-G jenkins' arguments to the docker service config file. For example, on centos6, I updated the following file: cat /etc/sysconfig/docker # Docker Upstart and SysVinit configuration file # Customize location of Docker binary (especially for development testing). DOCKER="/usr/bin/docker" 0 # Use DOCKER_OPTS to modify the daemon startup options. DOCKER_OPTS=' --host=unix:///var/run/docker.sock --restart=false -g /opt/app/jenkins/docker -G jenkins' and it resulted to the following permissions: srw-rw---- 1 root jenkins 0 Jan 5 12:22 docker.sock

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.