-
Notifications
You must be signed in to change notification settings - Fork 152
Better handling of secondary volumes size #361
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
Comments
This causes issues with image builder if you have a base image > 50GB. It would be a lot more complicated, but it would be better, if possible to detect the size of the primary image first before adding in a secondary. Easy repro steps:
|
clement-gilbert
pushed a commit
to clement-gilbert/scaleway-cli
that referenced
this issue
Mar 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some new offers have size limits, we should as often as possible create a secondary volume if not manually filled. This is the default behavior on the console for instance.
See #360 and scaleway/docker-machine-driver-scaleway#40
The text was updated successfully, but these errors were encountered: