-
Notifications
You must be signed in to change notification settings - Fork 290
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
Make disk available on tutorial vagrant images larger #392
Comments
Also, working out and specifying the minimum system requirements to be able to successfully follow and complete the tutorial might be useful. |
I just had a quick look into this and it appears to be more difficult than it should be. vagrant people recommend you implement a VirtualBox specific post-build hook to resize the Vdi file. See hashicorp/vagrant#2339 (comment) But unhelpfully, they don't actually document how exactly to to that and some others have commented that it's more difficult because you first need the ID of the virtual disk device; and vagrant doesn't make that available. See hashicorp/vagrant#2339 (comment) The tutorial is based on our own flocker-dev image which in turn is based on a custom fedora image. |
The vagrant file for that image is in the description on vagrantcloud. |
Before going too far down this path let's see if we can just get a smaller mongo docker image. I don't want to change too much at this point if we can help it. |
@dwgebler how are you getting on with this? |
I'm at least 50% hopeful #383 will be working today. |
I just ran out of disk space again on our vagrant dev environment and this docker bug may be the culprit. I'd removed all containers and all images and yet there were still lingering data directories for old mongo containers. Removing all the vfs sub-directories freed up the space.
|
We are moving our development planning to JIRA. This issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-392. You are welcome to file additional issues in GitHub if that's easier for you. |
Replaced by https://clusterhq.atlassian.net/browse/FLOC-392
Currently image is 9GB and it's very easy to run out of space, which tends to break everything going forward. Increasing available size won't increase download time so there's no real cost.
The text was updated successfully, but these errors were encountered: