Machine create fails with latest Docker #4156
Comments
Same problem here
Yesterday the same command worked fine with docker version 17.05.0-ce |
I can confirm this too:
|
I'm using this as a workaround: docker-machine create or |
I have the same issue. docker version : Docker version 17.06.0-ce
Jun 29 12:26:56 ip-172-31-10-149 systemd[1]: Starting Docker Application Container Engine...
|
I was able to get it working with this PR Just compile docker-machine with this fix and everything works again |
@gnomus super, that's interesting! I wonder why it was working for 17.05.0-ce, though. @therealppa haahaha awesome! I was wondering how I might get the old version of that script, or whether the live script takes params to install older version. web.archive.org definitely didn't not occur to me. |
@dminkovsky I don't think it will work forever, if you look into the script it doesn't actually specify the version anywhere... Still, right now it works. |
@therealppa @dminkovsky A longer term fix is to change the line 457 of the script from
to
Hopefully the fixed version of docker-machine is released soon. |
same for me |
@fabio-barile what about the |
@dminkovsky I had the same problem on a autoscaling ci with gitlab, got the aufs problem + dockerd problem, had to solve it with specifying overlay in the storage driver. |
Beyond the storage driver issue I'm also seeing verification errors for certificates created by gitlab-runner (9.3.0). @JustEra have you been running into the same issue or am I the only one?
|
This fixed storage-driver issue for me (just removed that parameter; for systemd ONLY). Apply on top of #4128 and re-build:
|
For anyone who wants a specific older version, we (Rancher) maintain slightly modified get.docker.com scripts to install each one: http://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions |
@fabio-barile above is entirely correct. How 'testing' lets such things be emitted, can't imagine. More information here: docker/for-linux#11 (comment) @vincent99 ...always like the sound of you guys, and thanks. |
+1 For now, I add /etc/systemd/system/docker.service.d/20-machine.conf which overrides 10-machine.conf with the correct command line. That way further docker-machine command which would normally break it, doesn't. Of course the longer it takes for this to be fixed in the release, the more work I have putting everything back! |
Thanks for the great breakdown of details on the issue - We're looking into it to try and figure out what went wrong. related to docker/for-linux#11 (comment) |
So this is not related to the install script at This PR (#4128) seems to remedy this issue and I'll have a PR up by late afternoon that adds tests for the other comparison functions so that we don't run into something like this again. |
Relates to issues raised in docker#4156 Signed-off-by: Eli Uriegas <seemethere101@gmail.com>
Relates to issues raised in docker#4156 Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
@seemethere Sounds good, thanks. Like to hear about the test. The diff on one of the PRs appeared a little odd to me, but think you guys will have taken care of that. |
@dminkovsky Can you create a new issue for this? It's unrelated to the |
@shin- i'm all good. docker-machine is working 100% right now for me. are you referring to the overlay2 thing? |
My other issue regarding removing machines was addressed in pr #4187. Thx. |
@dminkovsky Sorry - yes, the one you mention here |
@shin - After experiencing the issue in #4168, I attempted to re-create my staging server and found a slough of issues with
Are these all related? Start tracking these here? I can confirm that this issue is still happening today. |
@shin- docker-machine v0.12.1 exhibits the same issue still |
Please update to the latest release found on github: |
Thank you @dminkovsky I was getting this error on 0.12.2 today as well!!! Seems like |
You're welcome!
I specify "overlay" in the command line option for storage engine and since
the my machines boot.
ср, 2 авг. 2017 г. в 12:05, Denis <notifications@github.com>:
… Thank you @dminkovsky <https://github.com/dminkovsky> I was getting this
error on 0.12.2 today as well!!! Seems like 10-machine.conf file does not
get overridden during update
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4156 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANWZSYqy1uGhWeXozx35OnFhPRSb144ks5sUJ5YgaJpZM4OIt7R>
.
|
If using systems with kernel >4.4 I suggest using |
I wasn't able to get the machine to use overlay2, and the use case for this
fortunately was just building/CD
ср, 2 авг. 2017 г. в 12:36, Seweryn Zeman <notifications@github.com>:
… If using systems with kernel >4.4 I suggest using overlay2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4156 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANWZXLGHjLvfOOAgmBWV0zOEBDZBdSVks5sUKWBgaJpZM4OIt7R>
.
|
Also getting this error on 0.12.2 :-( |
this still opened! |
I still see this issue with For some reason, this still fails to start docker, but rebooting the machine then solves it. |
Can confirm, still the same error |
@jhartma I guess is necessary upgrade to latest release (linux image) and works |
@kassanmoor seems my AMI didn't support it on AWS, I got it to work with the default one |
Hello
docker-machine version 0.12.0, build 45c69ad
docker-machine create
fails now:The machine is created and Docker is installed, but it won't start. The problem appears to be a related to a new version of Docker getting installed by a new version of the install script over at https://get.docker.com. My installs went from 17.05.0-ce to 17.06.0-ce, and with that change, Docker installs but does not start.
or
Unless I change:
to
in
/etc/systemd/system/docker.service.d/10-machine.conf
.The text was updated successfully, but these errors were encountered: