If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see CONTRIBUTING.md.

You don't have to include this information if this is a feature request

(This is an automated, informational response)

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:

docker version:
docker info:

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

----------END REPORT ---------

#ENEEDMOREINFO

When I'm accessing the Jenkins-container and try to perform a Docker-command

Can you show the exact steps? Is this error inside the container? Are you running docker-in-docker?

@lorenzvth7, I encountered the same problem while using the image jenkins from rancher catalog where by default they use to bind-mount docker inside the container

volumes:
- '/var/run/docker.sock:/var/run/docker.sock'
- '/usr/bin/docker:/usr/bin/docker'

In my case my os was centos and inside the container the os is debian so docker won't work.

I fix this by installing proper docker binary inside the jenkins(debian) container and only bind-mound the docker socket.

Yes, if you installed docker from the official apt/yum repos, then it is a dynamically linked binary and just bind-mounting it into the container isn't enough to make it work.

I'm going to close this issue, because (as @cpuguy83 explained) this looks like a user error, but feel free to comment here after I've closed

@cpuguy83 How can you make it then?

@thaJeztah @cpuguy83 @kevinsimper It was indeed a user-error. I had to mount the shared object files.

Yes, but a found the solution. It is just to download the docker binary and use that, since it is only the client you need inside the container 👍

@kevinsimper in case it's useful; there's also official images containing docker; https://hub.docker.com/_/docker/

@thaJeztah Nice, thanks you! :)

@kevinsimper by just downloading the docker binary, do you mean doing something like apt-get install docker-engine?

@tnguyen14 It is the opposite you want, you can just grab it from github release https://github.com/docker/docker/releases

@kevinsimper @tnguyen14 you can get it even easier; use the official docker image on Docker Hub; https://hub.docker.com/_/docker/

(just realized I already mentioned that above, haha)

@thaJeztah I needed the docker client inside my node.js app, so I needed the cli directly :)

@thaJeztah True, but I'm trying to get the docker client inside a jenkins image, which is not based off of the docker image. Unless there is a way to somehow replicate the features from the docker image?

@kevinsimper I ended up doing RUN curl -L https://get.docker.com/builds/Linux/x86_64/docker-latest > /usr/bin/docker && chmod +x /usr/bin/docker

@tnguyen14 just a heads up; with docker 1.11, docker is shipped as multiple binaries, and static binaries will be shipped as a .tgz archive, so it's best to pin your script to a specific version (instead of docker-latest), and update your script to work with the archive, once you're switching to 1.11

Thanks for the heads up @thaJeztah. I modified my script to be RUN curl -L https://get.docker.com/builds/Linux/x86_64/docker-1.10.3 > /usr/bin/docker && chmod +x /usr/bin/docker