-
Notifications
You must be signed in to change notification settings - Fork 34
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
problem with creating new docker-machine #63
Comments
Actually, the issue was not fixed. I still see that problem. And my PR was about removing IP, not creating instances.
|
Github closes this issue, @bchatelard can you check the public status of bootscripts ? |
@QuentinPerez two docker bootscripts were available one 4.9.20 and one 4.10.8 Having two docker bootscripts available is valid for me, i believe the issue here is how the server is created. |
Probably too late to answer but I had same issue as @QuentinPerez had. Using image ID fixes the issue, I believe it's linked with Scaleway service specifics. |
Hi. I have problem with creating new VM by scaleway docker-machine driver.
There is part of debug output:
There is output from
"[GET]: https://cp-par1.scaleway.com/bootscripts"
:Big json
some text
I was tried to fix it by setting defaultBootscript variable to
8fd15f37-c176-49a4-9e1d-10eb912942ea
(I found that ID here). But it fail with start docker on instance. There is output from journalctl:So, I try older bootscript
cd65a9a3-b9db-4b3f-85a7-9aaa9e29d5da
and it was fixed my problem, but I don't think it is a permanent solution.The text was updated successfully, but these errors were encountered: