[JIRA] (JENKINS-46799) Blueocean Docker Pipeline Failed | Cannot start docker container

[enric.prats@gmail.com (JIRA)]

Enric Prats updated an issue

Jenkins / JENKINS-46799 Blueocean Docker Pipeline Failed | Cannot start docker container Change By: Enric Prats Priority: Major Minor Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[enric.prats@gmail.com (JIRA)]

Enric Prats reopened an issue

Marcelo Tocchetto workaround is good but people should not have to change the docker image once downloaded and running.  This should be changed on the Dockerfile which builds the image

Jenkins / JENKINS-46799 Blueocean Docker Pipeline Failed | Cannot start docker container

Change By: Enric Prats Resolution: Not A Defect Status: Closed Reopened

Add Comment

[enric.prats@gmail.com (JIRA)]

Enric Prats edited a comment on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container [~mtocchetto] workaround is good but people should not have to change the docker image once downloaded and running.  This should be changed on the Dockerfile which builds the image .   It's enough to add to the Jenkinsfile:     # Allow Jenkins to run docker commands     chown :jenkins /var/run/docker.sock   I will try to figure how to make the pull request but I have never made one :(

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan commented on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container

I'm pretty sure you can use `--group-add` (I have it setup on my instance, I just forgot if this is why) on my system docker group is 978 `getent group docker | awk -F: '{print $3}'` so the following will make the jenkins user (which the container runs as) also have the GID of 978 docker run -v /var/run/docker.sock:/var/run/docker.sock --group-add 978 -p 8080:8080 --name jenkins_blueocean jenkinsci/blueocean:latest

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan commented on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container

I just tried it on my ubuntu laptop, group-add 999 and seems to work.

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan updated an issue

Jenkins / JENKINS-46799

Blueocean Docker Pipeline Failed | Cannot start docker container

Change By: Gavin Mogan Attachment: image-2019-02-08-15-23-14-655.png

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan commented on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container I think the key is --group-add takes in a GID, not a group name

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan commented on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container

My bad, it does take in groups, but maps it to the containers group name, not the host's group names docker run --rm -v /var/run/docker.sock:/var/run/docker.sock --group-add 999 -p 8080:8080 --name jenkins_blueocean --entrypoint "" jenkinsci/blueocean:latest id uid=1000(jenkins) gid=1000(jenkins) groups=1000(jenkins),999(ping) vs docker run --rm -v /var/run/docker.sock:/var/run/docker.sock --group-add 999 -p 8080:8080 --name jenkins_blueocean --entrypoint "" jenkinsci/blueocean:latest id    uid=1000(jenkins) gid=1000(jenkins) groups=1000(jenkins),999(ping)

Add Comment

[gmogan@cloudbees.com (JIRA)]

Gavin Mogan closed an issue as Not A Defect

Jenkins / JENKINS-46799

Blueocean Docker Pipeline Failed | Cannot start docker container

Change By: Gavin Mogan Status: Reopened Closed Resolution: Not A Defect

Add Comment

[alcmaeon@gmail.com (JIRA)]

Enrique Diaz commented on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container That solved one issue, but now I get  + docker inspect -f . node:6-alpine Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/node:6-alpine/json: dial unix /var/run/docker.sock: connect: permission denied The usual comment to address this is to do ---> sudo usermod -a -G docker $USER But that is not an option in mac. Any suggestions? Kind Regards.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[alcmaeon@gmail.com (JIRA)]

Enrique Diaz edited a comment on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container

That solved one issue, but now I get   the following problem:

+ docker inspect -f . node:6-alpine Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get [http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/node:6-alpine/json]: dial unix /var/run/docker.sock: connect: permission denied The usual comment to address this is to do ---> sudo usermod -a -G docker $USER But that is not an option in mac. Any suggestions? Kind Regards.

Add Comment

[alcmaeon@gmail.com (JIRA)]

Enrique Diaz edited a comment on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container

That solved one issue, but now I get the following problem: + docker inspect -f . node:6-alpine Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get [http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/node:6-alpine/json]: dial unix /var/run/docker.sock: connect: permission denied

-------------------------

The usual comment to address this is to do ---> sudo usermod -a -G docker $USER But that is not an option in mac. Any suggestions? Kind Regards.

Add Comment

[alcmaeon@gmail.com (JIRA)]

Enrique Diaz edited a comment on JENKINS-46799

Re: Blueocean Docker Pipeline Failed | Cannot start docker container

That solved one issue, but now I get the following problem:

+ docker inspect -f . node:6-alpine

Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get [http://%2Fvar%2Frun%2Fdocker.sock/v1.39/containers/node:6-alpine/json]: dial unix /var/run/docker.sock: connect: permission denied [Pipeline] isUnix[Pipeline] sh

------------------------- The usual comment to address this is to do ---> sudo usermod -a -G docker $USER But that is not an option in mac. Any suggestions? Kind Regards.

Add Comment