nanobox-io / nanobox-boot2docker-old

boot2docker nanobox Vagrant Box

This repository contains the scripts necessary to create a Vagrant-compatible boot2docker box for nanobox.

Usage

If you want the actual box file, you can download it from the releases page.

Building the Box

If you want to recreate the box, rather than using the binary, then you can use the scripts and Packer template within this repository to do so in seconds.

To build the box, first install the following prerequisites:

• Packer (at least version 0.5.1)
• VirtualBox (at least version 4.3), VMware, or Parallels
• Vagrant

Then follow the steps:

$ vagrant up
...
$ vagrant destroy --force
...
$ packer build template.json
...

Note: To use the newly created box, you may need to remove any old boxes from vagrant.
Find with vagrant box list and remove with vagrant box remove $NAME

License

Mozilla Public License, version 2.0

nanobox-boot2docker-old's Issues

How to install the box offline?

Hi,

I have downloaded the nanobox-boot2docker from release to my computer. I was wondering if I can use the below command to install the box? Is this enough or I should use other commands?

nonabox box install path-to-directory/nanobox-boot2docker

I can not install it using the standard way because the download fails.

Nanobox can't mount directories properly

Earlier today, I updated the nanobox/boot2docker box in order to resolve a different issue with nanobox-io/nanobox. Unfortunately this caused something in mounts to break. This results in the following error message:

Failed to mount folders in Linux guest. This is usually because
the "vboxsf" file system is not available. Please verify that
the guest additions are properly installed in the guest and
can work properly. The command attempted was:
2015-11-10 17:17:23 ERROR mount -t vboxsf -o uid=`id -u docker`,gid=`getent group docker | cut -d: -f3` mnt_ssh /mnt/ssh
mount -t vboxsf -o uid=`id -u docker`,gid=`id -g docker` mnt_ssh /mnt/ssh
2015-11-10 17:17:23 ERROR The error output from the last command was:
2015-11-10 17:17:23 ERROR mount.vboxsf: mounting failed with the error: No such device
mount: mounting mnt_ssh on /mnt/ssh failed: No such device

I have tracked it down to a missing kernel module vboxsf

$ lsmod | grep -i vbox
vboxguest             180224  0 

A patch is forthcoming that will add the module but for now if you vagrant ssh in, you can add it by running $ sudo modprobe -a vboxsf

`nanobox run` (0.15.6) apparently downloads box image that does not boot

At first glance, seems like it doesn't even have a boot sector.

If it matters, I did the standalone nanobox tool installation, using my system copy of Vagrant (1.7.4) and Virtualbox (5.0.8).

I haven't yet tried peeling apart the VMDK (booting a GNU Parted image or something against the VM and looking around), nor have I tried manually rebuilding it.

increase boot2docker ulimit

currently, the default ulimit for tcp sockets is 1024. This needs to be updated to something much higher.

docker env var's

nanobox-server needs access to the DOCKER_HOST env var