From 161cc21f245cf05c6c2c168a6f5981989026e2cb Mon Sep 17 00:00:00 2001 From: Hollie Teal Date: Tue, 26 Aug 2014 14:01:10 -0700 Subject: [PATCH] Final changes. Signed-off-by: Hollie Teal --- docs/sources/articles/b2d_volume_resize.md | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/docs/sources/articles/b2d_volume_resize.md b/docs/sources/articles/b2d_volume_resize.md index 8ed4cdafa7..5ee0d21f49 100644 --- a/docs/sources/articles/b2d_volume_resize.md +++ b/docs/sources/articles/b2d_volume_resize.md @@ -6,13 +6,13 @@ 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, your pulls might start failing with "no space left on device" errors when -the Boot2Docker VM's volume runs out of space. The solution is to increase the volume size by +the Boot2Docker VM's volume fills up. 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) since it's a free ISO and works well with VirtualBox. -## 1. Stop Boot2Docker’s VM +## 1. Stop Boot2Docker Issue the command to stop the Boot2Docker VM on the command line: @@ -27,7 +27,7 @@ Using the command line VirtualBox tools, clone the VMDK image to a VDI image: $ vboxmanage clonehd /full/path/to/boot2docker-hd.vmdk /full/path/to/.vdi -—format VDI -—variant Standard -## 3. Resize the VDI volume you created +## 3. Resize the VDI volume 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: @@ -67,15 +67,15 @@ the top of the **Boot Order** list. ## 7. Boot to the disk partitioning ISO -Manually start the Boot2Docker VM, and the disk partitioning ISO should start up. +Manually 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 +up and display the 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**, +Drag the slider representing the volume to the maximum available size, click **Resize/Move**, and then **Apply**. @@ -85,9 +85,11 @@ the Boot2Docker VM in VirtualBox. ## 8. Start the Boot2Docker VM -Fire up the Boot2Docker VM manually in VirtualBox. The VM should log in automatically, but the credentials are ``docker/tcuser`` if it doesn't. Using the ``df -h`` command, verify that your changes took effect. +Fire up the Boot2Docker VM manually in VirtualBox. The VM should log in automatically, but +the credentials are ``docker/tcuser`` if it doesn't. Using the ``df -h`` command, verify +that your changes took effect. - + You’re done!