-
Notifications
You must be signed in to change notification settings - Fork 111
Docker client API version is too old #33
Comments
Just hit the same issue with CentOS 7.1
|
The problem escalated to CoreOS Beta Channel in the last week. Is this software still actively maintained @ibuildthecloud ? |
Seeing this with CentOS 7.1 too.
Work around for me right now is to downgrade to 1.6.2.
|
all u have to do is to change 1.11 to 1.12 in line 265 main.go - which few people already did in their own forks (ex: github.com/agend07/systemd-docker) then use build script and use the binary |
@agend07 Thanks! It worked for me |
What happens if you have a generic unit file and people grab that and run it on docker 1.6 after you've updated to 1.12 on main.go? Will it break and crash into a horrible mess? |
The current API Version is greater than 1.19. It seems that the server will also support some old version. The updated api-version in the main.go is the minimum api version. docker version |
Thanks. I've decided not to use systemd-docker for fear of breaking things later. It's a hack that isn't really necessary if you don't mix the use of systemd and docker together. |
@hookenz Yes, the new release breaks on Docker 1.6.2 for me. The API version change seems not backwards compatible. Keeping the older systemd-docker on servers with the older Docker version for now. Kind of a mess. |
I'm getting the following error with the docker version shipped with CoreOS alpha images (1.7.1):
"client is too old, minimum supported API version is 1.12"
Not sure if the fix is trivial (just a version bump) or if more care is needed to update the API calls.
The text was updated successfully, but these errors were encountered: