-
Notifications
You must be signed in to change notification settings - Fork 41
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
Multi disk support #91
Comments
Thanks for the report @Katana-Steel . That's a known limitation right now, but if anyone wants to add support for multiple disks it's definitely welcome. |
@Katana-Steel Could you share an example of a box with two disks? |
I have the vagrant box image which is hosted on s3: I can get to my vagrant file tomorrow, mutate converted box-disk1 of the On Aug 15, 2016 7:43 PM, "Steve Wills" notifications@github.com wrote:
|
|
This also applies to ubuntu/xenial64 that uses 2nd disk as a configdrive, and not converting this |
any interest in this issue? |
Confirming this affects the Ubuntu cloud-image boxes since they are for VirtualBox and contain 2 disk images: the root-fs and the cloud-init data. E.g the ubuntu/bionic64 image when mutated results in:
|
Thank you @iam-TJ it would be nice if vagrant-mutate would support extra disk images. |
I've just about finished adding the functionality - need to do some thorough testing then I'll publish the code in my forked repo. Have had to give myself a crash-course in Ruby, and Vagrant! Tracking it here: |
See: #1 See: sciurus#91
@iam-TJ if you're interested in maintaining vagrant-mutate I'd be happy to give you commit access here! |
I got a VirtualBox .box with 2 disks, but running it through mutate only converted the
1st disk from the box.ovf file
(meaning I could boot the VM but it's data disk wasn't available)
The text was updated successfully, but these errors were encountered: