0ct0pu5/moby
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Added Fred's suggestions.

Browse source 
Signed-off-by: Hollie Teal <hollie@docker.com>
This commit is contained in:
Hollie Teal 2014-08-27 11:49:26 -07:00
parent 161cc21f24
commit 77ca0ae9de
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/sources/articles/b2d_volume_resize.md
View file

@ -9,14 +9,14 @@ with are very large, your pulls might start failing with "no space left on devic
the Boot2Docker VM's volume fills up. 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. first cloning it, then resizing it using a disk partitioning tool.
We'll use [GParted](http://gparted.sourceforge.net/download.php/index.php) We recommend [GParted](http://gparted.sourceforge.net/download.php/index.php)-- the ISO
since it's a free ISO and works well with VirtualBox. is a free download and works well with VirtualBox.
## 1. Stop Boot2Docker ## 1. Stop Boot2Docker
Issue the command to stop the Boot2Docker VM on the command line: Issue the command to stop the Boot2Docker VM on the command line:
$ boot2docker stop `$ boot2docker stop`
## 2. Clone the VMDK image to a VDI image ## 2. Clone the VMDK image to a VDI image
@ -25,21 +25,21 @@ instead create a VDI volume and clone the VMDK volume to it.
Using the command line VirtualBox tools, clone the VMDK image to a VDI image: 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/<newVDIimage>.vdi -—format VDI -—variant Standard `$ vboxmanage clonehd /full/path/to/boot2docker-hd.vmdk /full/path/to/<newVDIimage>.vdi -—format VDI -—variant Standard`
## 3. Resize the VDI volume ## 3. Resize the VDI volume
Choose a size that will be appropriate for your needs. If you’re spinning up a lot of containers, 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: or your containers are particularly large, larger will be better:
$ vboxmanage modifyhd /full/path/to/<newVDIimage>.vdi —-resize <size in MB> `$ vboxmanage modifyhd /full/path/to/<newVDIimage>.vdi —-resize <size in MB>`
## 4. Download a disk partitioning tool ISO ## 4. Download a disk partitioning tool ISO
To resize the volume, you'll need a disk partitioning tool like [GParted](http://gparted.sourceforge.net/download.php/). To resize the volume, we'll use [GParted](http://gparted.sourceforge.net/download.php/).
Once you've downloaded the tool, add the ISO to the Boot2Docker VM’s IDE bus. 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. **Note:** It's You might need to create the bus before you can add the ISO. **Note:** It's
important that the partitioning tool you choose is available as an ISO so that important that you choose a partitioning tool that is available as an ISO so that
the Boot2Docker VM can be booted with it. the Boot2Docker VM can be booted with it.
<table> <table>
@ -86,7 +86,7 @@ the Boot2Docker VM in VirtualBox.
## 8. Start the Boot2Docker VM ## 8. Start the Boot2Docker VM
Fire up the Boot2Docker VM manually in VirtualBox. The VM should log in automatically, but 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 if is doesn't, the credentials are `docker/tcuser`. Using the `df -h` command, verify
that your changes took effect. that your changes took effect.
<img src="/articles/b2d_volume_images/verify.png"> <img src="/articles/b2d_volume_images/verify.png">