Closed larrycai closed 8 years ago
Further I tried to use host docker binary (shall be recommended ??) with
docker run -v /usr/bin/docker:/usr/bin/docker -v /var/run/docker.sock:/docker.sock --privileged=true --pid=host --net=host dreamcat4/pipework --help
Then it reports
mkdir: cannot create directory '/sys/fs/cgroup': No such file or directory mount: mount point /sys/fs/cgroup does not exist Could not make a tmpfs mount. Did you use -privileged?
No clue how to go further
Hi. That last error msg is not expected from this issue. Like its not using privileged mode for some other reason in your prod environement.
Aparrently dreamcat4/pipework:1.1.3
runs docker v1.7.1. So Either use that, or rebuild the newest version yourself from master for a latest pipework image on docker v1.7.1.
See other issue 17
Yes as you said, the later error message about cgroups is related with the configuration on my docker host (redhat6.5)
tag 1.1.3
works as well in my local docker toolbox environment.
Thx,
Ok glad to hear it.
just add comments on how to rebuild for the 1.7.1 version, you need to change the Dockerfile
apt-get install -qqy lxc-docker-1.7.1
Ah ok. Maybe I could do that after taking your PR on master? (ie start building both versions).
Or if you prefer, I would more appreciate you to fork my project, and start building the 1.7.1 variant for everybody. Since I dont plan on adding any new features anymore.
so far, what I did
The best way I suggest to have separate branch for 1.7.1 with modified Dockerfile in your repo as well, then you can build two version easily.
u2u
OK @larrycai. What I'm going to do is direct users to your 1.7.1 image instead. Because that is simpler and your work here is competent / very good.
new here.
It works fine in latest docker engine 1.10.x and docker compose 1.6.x (Windows DockerToolbox).
While when I use it "prod" env where docker engine 1.7.1 is used (I can't upgrade so far), no matter which version of docker-compose is used, it always reports
Here is env
I tried for docker-compose
1.5.2
/1.5.1
/1.4.2
, also tried with envCOMPOSE_API_VERSION
, it always reports this fault.Also noticed it is not related with
docker-compose
Do you have any suggestion ? (old docker image ?)