Skip to content

Instantly share code, notes, and snippets.

@dariusf
Created August 2, 2023 07:58
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dariusf/2261abfa057d697ec9bcf37a95b70f9e to your computer and use it in GitHub Desktop.
Save dariusf/2261abfa057d697ec9bcf37a95b70f9e to your computer and use it in GitHub Desktop.
VirtualBox for Docker users

VirtualBox for Docker users

Sometimes you need VirtualBox instead of Docker - when more isolation is required, or because a desktop environment is too hard to configure.

(Updated Sep 2021)

Getting Started

brew install --cask virtualbox

There's no equivalent of docker run -it to start a VM and give me a shell; we'll have to use ssh.

Import the image, the equivalent of docker load. This takes about a minute for a 4GB image.

vboxmanage import vm.ova

# `vm` from now on is the name of our virtual machine, which we can confirm with
vboxmanage list vms

# port forward, so we can use ssh. the first port is the host's
vboxmanage modifyvm vm --natpf1 "ssh,tcp,,2222,,22"

# power it on
vboxmanage startvm vm
vboxmanage startvm vm --type headless

# now it appears here
vboxmanage list runningvms

# wait for the VM to start, then
ssh -p 2222 user@127.0.0.1

At this point we can interactively get the VM into the state we want, or write a script to automate it. The subcommand for the latter is guestcontrol, similar to docker exec.

vboxmanage guestcontrol vm run /bin/sh --username user --password pass --verbose \
  --wait-stdout --wait-stderr -- -c "echo test"

The docs say that stdin is forwarded, but it seems signals aren't, so I couldn't get a piped shell script to run. We can work around that somewhat with the guestcontrol copyto subcommand.

vboxmanage guestcontrol vm copyto --verbose --username user --password pass host-dir \
  --target-directory /home/vm

When we're done, we'll want to power the VM off, export the new state back to an ova file if necessary, then delete it.

vboxmanage controlvm vm poweroff
vboxmanage export vm -o vm1.ova
vboxmanage unregistervm vm --delete

Mounted Volumes (aka Shared Folders)

It seems we don't need the Guest Additions CD here.

First, tell VirtualBox about the shared folder. We'll have to power off for this.

vboxmanage sharedfolder add vm --name share --hostpath ~/Downloads/shared

# we see it here
vboxmanage showvminfo vm

Inside the VM, we get to pick where we want to mount the shared folder.

# create the directory we want to mount at
mkdir /home/user/shared

# add ourselves to the vboxsf group
sudo usermod -a -G vboxsf user

sudo mount -t vboxsf -o uid=$(id -u),gid=$(id -g),rw share /home/user/shared  

Powering the VM off unmounts the shared folder, but we can also do it manually.

sudo umount /home/user/shared

Snapshots

I've not found many opportunities to use docker checkpoint, but snapshots get a special mention because they're a very useful part of VirtualBox, and the interface is nice and intuitive.

vboxmanage snapshot vm list
vboxmanage snapshot vm take s
vboxmanage snapshot vm restore s
vboxmanage snapshot vm delete s
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment