0.5.4 release doesn't mount a persistent partition for images

[fnichol]

Looks like rootfs is being run off the RAM disk which is where docker images are being written to. So a 512MB VM gives you a rootfs of ~512MB.

Too tired to follow through on this, but I will try to be more helpful in the morning checking upstream in boot2docker.

[lhoBas]

Noticed that a /dev/sda1 disk is being shown (plain 0.5.4 release init & up, VMware Fusion). Do not see any references to it in the Vagrant template, but there is an additional disk hooked up to the VM. Not mounted or recognized by the automount rc script.

Not entirely clear to me whether this disk is generated upstream by boot2docker (as in: copied from iso), or generated by the script in this repo. Does the vmdisk get copied while repacking the iso?

[drnic]

And here's a picture:

$ df
Filesystem                Size      Used Available Use% Mounted on
rootfs                  446.0M    320.8M    125.2M  72% /
tmpfs                   247.8M     12.0K    247.8M   0% /dev/shm
none                    446.0M    320.8M    125.2M  72% /var/lib/docker/aufs/mnt/536488468dd283b53ca54bc25949f37aca1f812964cfc792b01ee89161a23394

[lmars]

@fnichol I've just opened a PR to fix this: #21

[mitchellh]

Fixed!

[fnichol]

Nice work team!