Closed tobiasmuehl closed 4 years ago
Same error with the DEV1-S
:
docker-machine create -d scaleway --scaleway-commercial-type="DEV1-S" --scaleway-name="test" --scaleway-volumes="20G" --scaleway-debug test
Running pre-create checks...
Creating machine...
(test) Creating SSH key...
(test) Creating server...
(test) Starting server...
Error creating machine: Error in driver during machine creation: StatusCode: 400, Type:
invalid_request_error, APIMessage: The total size of local-volume(s) of instances DEV1-S must be equal to 20GB
The result is an instance with two volumes with a total of 70 GB.
Thanks for any info.
Any help from Scaleway team? @QuentinPerez @moul
Following this blog post, and the readme produce the same error as describe above by @tobiasmuehl and @aurels
There is any way to solve this issue or a workaround?
For exemple, when I run:
docker-machine create -d scaleway --scaleway-name="swc-docker" --scaleway-commercial-type="DEV1-S" --scaleway-volumes="20G" --scaleway-token=TOKEN --scaleway-organization=ID --scaleway-debug docker
It create the instance volume of 20GB plus a 50GB snapshot. It's because this snapshot that the error occurs?
Thanks
running the first example:
docker-machine create -d scaleway --scaleway-token=TOKEN --scaleway-organization=ID my-scaleway-docker-machine
I'm getting the follow error:
Running pre-create checks...
Creating machine...
(docker-test) Creating SSH key...
(docker-test) Creating server...
Error creating machine: Error in driver during machine creation: StatusCode: 403, Type: invalid_request_error, APIMessage: Quota exceeded for this resource.
This is still happening. Could anyone from scaleway comment ?
+1
+1 really confused about this :confused:
I get multiple volumes when launching a machine and the --scaleway-volumes
seems to be ignored?
When creating a machine via:
docker-machine create -d scaleway --scaleway-token=xxxxx --scaleway-organization=xxxxx --scaleway-commercial-type "GP1-XS" --scaleway-region "par1" cloud-scaleway
I get multiple volumes (top two volumes in the screen below):
The same machine created via the dashboard console yields a single volume of 150GB
.
Hi, Sorry for the inconvenience.
Since our new scaleway-sdk-go is approaching a stable state, a total rewrite of the driver has begun. It will support all instance types, fix known issues and introduce new instance features.
You can feel confident that all opened issues will be taken into account for this version 2.
Have a look at the work on #104 and the related PR: #105.
Thanks a lot for your contributions and feedback! Stay tuned! 🤘
hey @QuentinBrosse, good to know that there is a working in progress to address this issue. Do you have any timeline to get a first release of the driver? I have a tight timeline to make a final decision to go with Scaleway or another docker hosting. Thanks
Hi @tmoreira2020,
I don't have a precise timeline but, in the Q1 of 2020.
Thanks @QuentinBrosse for the feedback, unfortunately this is too late for us to wait. As a workaround I'm thinking to patch the current version to create DEV1-S with 20GB and not 50GB. I believe 50GB is hardcoded on some place in the source code? Do you know where it is?
Perhaps if I hardcode 20GB in the size
parameter do the trick here: https://github.com/scaleway/docker-machine-driver-scaleway/blob/a2f88d2c2645ef751171a954236ab4f32419b269/vendor/github.com/scaleway/scaleway-cli/pkg/api/helpers.go#L428
What do you think?
Also happens with
--scaleway-volumes 25000000000