mirror of
https://github.com/moby/moby.git
synced 2022-11-09 12:21:53 -05:00
Additional formatting and markdown changes to B2D volume resize doc
Signed-off-by: Hollie Teal <hollie@docker.com>
This commit is contained in:
parent
db3db49e9c
commit
e4ff140fdd
2 changed files with 43 additions and 18 deletions
|
@ -92,7 +92,7 @@ pages:
|
|||
- ['articles/ambassador_pattern_linking.md', 'Articles', 'Cross-Host linking using Ambassador Containers']
|
||||
- ['articles/runmetrics.md', 'Articles', 'Runtime metrics']
|
||||
- ['articles/baseimages.md', 'Articles', 'Creating a Base Image']
|
||||
- ['articles/b2d_volume_increase', 'Articles', 'Increasing a Boot2Docker Volume']
|
||||
- ['articles/b2d_volume_resize.md', 'Articles', 'Increasing a Boot2Docker Volume']
|
||||
|
||||
# Reference
|
||||
- ['reference/index.md', '**HIDDEN**']
|
||||
|
|
|
@ -7,39 +7,64 @@ page_keywords: boot2docker, volume, virtualbox
|
|||
If you're using Boot2Docker with a large number of images, or the images you're working
|
||||
with are very large, you might run into trouble if the Boot2Docker VM's volume runs out of
|
||||
space. The solution is to increase the volume size by first cloning it, then resizing it
|
||||
using a disk partitioning tool. We'll use (GParted)[http://gparted.sourceforge.net/download.php/index.php]
|
||||
using a disk partitioning tool. We'll use [GParted](http://gparted.sourceforge.net/download.php/index.php)
|
||||
since it's a free ISO and works well with VirtualBox.
|
||||
|
||||
## 1. Stop Boot2Docker’s VM:
|
||||
## 1. Stop Boot2Docker’s VM
|
||||
|
||||
$ boot2docker stop
|
||||
|
||||
Boot2Docker ships with a VMDK image, which can’t be resized by VirtualBox’s native tools. We will instead create a VDI volume and clone the VMDK volume to it.
|
||||
Boot2Docker ships with a VMDK image, which can’t be resized by VirtualBox’s native tools. We will instead
|
||||
create a VDI volume and clone the VMDK volume to it.
|
||||
|
||||
## 2. Using the VirtualBox command line tools, clone the VMDK image to a VDI image:
|
||||
## 2. Clone the VMDK image to a VDI image
|
||||
|
||||
$ vboxmanage clonehd /full/path/to/boot2docker-hd.vmdk /full/path/to/<newVDIimage>.vdi —format VDI —variant Standard
|
||||
Using the command line VirtualBox tools, clone the VMDK image to a VDI image:
|
||||
|
||||
## 3. Resize the new clone volume, choosing a size that will be appropriate for your needs. If you’re spinning up a lot of containers, or your containers are particularly large, larger will be better:
|
||||
$ vboxmanage clonehd /full/path/to/boot2docker-hd.vmdk /full/path/to/<newVDIimage>.vdi -—format VDI -—variant Standard
|
||||
|
||||
$ vboxmanage modifyhd /full/path/to/<newVDIimage>.vdi —resize <size in MB>
|
||||
## 3. Resize the new clone volume
|
||||
|
||||
## 4. Download a disk partitioning tool ISO, like (GParted)[http://gparted.sourceforge.net/download.php/]. Add the ISO to the Boot2Docker VM’s IDE bus. You might need to create the bus before you can add the ISO.
|
||||
Choose a size that will be appropriate for your needs. If you’re spinning up a lot of containers,
|
||||
or your containers are particularly large, larger will be better:
|
||||
|
||||
<img src="b2d_volume_images/add_new_controller.png>
|
||||
<img src="b2d_volume_images/add_cd/png">
|
||||
$ vboxmanage modifyhd /full/path/to/<newVDIimage>.vdi —-resize <size in MB>
|
||||
|
||||
## 5. Add the new VDI image to the Boot2Docker image in VirtualBox.
|
||||
## 4. Download a disk partitioning tool ISO
|
||||
|
||||
<img src="b2d_volume_images/add_volume.png">
|
||||
To resize the volume, you'll need a disk partitioning tool like [GParted](http://gparted.sourceforge.net/download.php/).
|
||||
Once you've downloaded the tool, add the ISO to the Boot2Docker VM’s IDE bus. You might need to
|
||||
create the bus before you can add the ISO.
|
||||
|
||||
## 6. Verify in the Settings for the Boot2Docker VM that CD/DVD is the at the top of the **Boot Order** list.
|
||||
<img src="/articles/b2d_volume_images/add_new_controller.png"></br>
|
||||
<img src="/articles/b2d_volume_images/add_cd.png">
|
||||
|
||||
<img src="b2d_volume_images/boot_order.png">
|
||||
## 5. Add the new VDI image
|
||||
|
||||
## 7. Start the Boot2Docker VM in VirtualBox, and the disk partitioning ISO should start up. Using GParted, choose the **GParted Live (default settings)** option. Choose the default keyboard, language, and XWindows settings, and the GParted tool will start up and display the new VDI volume you created. Right click on the VDI and choose **Resize/Move**. Drag the slider representing the volume to its maximum size, click **Resize/Move**, and then **Apply**. Quit GParted and shut down the VM. Remove the GParted ISO from the IDE controller for the Boot2Docker VM in VirtualBox.
|
||||
to the Boot2Docker image in VirtualBox.
|
||||
|
||||
## 8. Start the Boot2Docker VM, either in VirtualBox or using the command line (`boot2docker start`) to make sure the volume changes took effect.
|
||||
<img src="/articles/b2d_volume_images/add_volume.png">
|
||||
|
||||
## You’re done!
|
||||
## 6. Verify the boot order
|
||||
|
||||
In the **System** settings for the Boot2Docker VM, make sure that **CD/DVD** is the at the top of the **Boot Order** list.
|
||||
|
||||
<img src="/articles/b2d_volume_images/boot_order.png">
|
||||
|
||||
## 7. Boot to the disk partitioning ISO
|
||||
|
||||
Manually start the Boot2Docker VM, and the disk partitioning ISO should start up.
|
||||
Using GParted, choose the **GParted Live (default settings)** option. Choose the
|
||||
default keyboard, language, and XWindows settings, and the GParted tool will start
|
||||
up and display the new VDI volume you created. Right click on the VDI and choose
|
||||
**Resize/Move**. Drag the slider representing the volume to its maximum size, click
|
||||
**Resize/Move**, and then **Apply**. Quit GParted and shut down the VM. Remove
|
||||
the GParted ISO from the IDE controller for the Boot2Docker VM in VirtualBox.
|
||||
|
||||
## 8. Start the Boot2Docker VM
|
||||
|
||||
Either directly in VirtualBox or using the command line (`boot2docker start`), start the Boot2Docker
|
||||
VM to make sure the volume changes took effect.
|
||||
|
||||
You’re done!
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue