Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

report version compatibility issue on docker engine 1.7.1 #19

Closed
larrycai opened this issue Apr 1, 2016 · 9 comments
Closed

report version compatibility issue on docker engine 1.7.1 #19

larrycai opened this issue Apr 1, 2016 · 9 comments

Comments

@larrycai
Copy link
Contributor

larrycai commented Apr 1, 2016

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

pipework_1 | Error response from daemon: client is newer than server (client API version: 1.21, server API version: 1.19)

Here is env

$ docker version
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64

I tried for docker-compose 1.5.2/1.5.1/1.4.2, also tried with env COMPOSE_API_VERSION, it always reports this fault.

Also noticed it is not related with docker-compose

$ docker run -v /var/run/docker.sock:/docker.sock --privileged=true --pid=host --net=host   dreamcat4/pipework --help
Error response from daemon: client is newer than server (client API version: 1.21, server API version: 1.19)
error: can't connect to unix:///docker.sock

Do you have any suggestion ? (old docker image ?)

@larrycai
Copy link
Contributor Author

larrycai commented Apr 1, 2016

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

@dreamcat4
Copy link
Owner

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

@larrycai
Copy link
Contributor Author

larrycai commented Apr 5, 2016

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,

@larrycai larrycai closed this as completed Apr 5, 2016
@dreamcat4
Copy link
Owner

Ok glad to hear it.

@larrycai
Copy link
Contributor Author

larrycai commented Apr 6, 2016

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

@dreamcat4
Copy link
Owner

Ah ok. Maybe I could do that after taking your PR on master? (ie start building both versions).

@dreamcat4
Copy link
Owner

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.

@larrycai
Copy link
Contributor Author

larrycai commented Apr 6, 2016

so far, what I did

  1. fork and raise the PR issue #20, add support for macro PROJECT_NAME #21 to fix issue how to support project based network using variable in compose ? #20
  2. have separate branch 1.7.1 to have different Dockerfile
  3. auto build the docker image larrycai/pipework:1.7.1

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

@dreamcat4
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants