The fact that there's a lot of buzz is unmistakeable, though. So being familiar with the technology can't be a bad idea.
I'm running Tribblix, so running Docker natively is just a little tricky. (Although if you actually wanted to do that, then Triton from Joyent is how to do it.)
But there's boot2docker, which allows you to run Docker on a machine - by spinning up a copy of VirtualBox for you and getting that to actually do the work. The next thought is obvious - if you can make that work on MacOS X or Windows, why not on any other OS that also supports VirtualBox?
So, off we go. First port of call is to get VirtualBox installed on Tribblix. It's an SVR4 package, so should be easy enough. Ah, but, it has special-case handling for various Solaris releases that cause it to derail quite badly on illumos.
Turns out that Jim Klimov has a patchset to fix this. It doesn't handle Tribblix (yet), but you can take the same idea - and the same instructions - to fix it here. Unpack the SUNWvbox package from datastream to filesystem format, edit the file SUNWvbox/root/opt/VirtualBox/vboxconfig.sh, replacing the lines
# S11 without 'pkg'?? Something's wrong... bail.
errorprint "Solaris $HOST_OS_MAJORVERSION detected without executable $BIN_PKG !? I are confused."
exit 1
with
# S11 without 'pkg'?? Likely an illumos variant
HOST_OS_MINORVERSION="152"
and follow Jim's instructions for updating the pkgmap, then just pkgadd from the filesystem image.
Next, the boot2docker cli. I'm assuming you have go installed already - on Tribblix, "zap install go" will do the trick. Then, in a convenient new directory,
env GOPATH=`pwd` go get github.com/boot2docker/boot2docker-cli
That won't quite work as is. There are a couple of patches. The first is to the file src/github.com/boot2docker/boot2docker-cli/virtualbox/hostonlynet.go. Look for the CreateHostonlyNet() function, and replace
out, err := vbmOut("hostonlyif", "create")
if err != nil {
return nil, err
}
with
out, err := vbmOut("hostonlyif", "create")
if err != nil {
// default to vboxnet0
return &HostonlyNet{Name: "vboxnet0"}, nil
}
The point here is that , on a Solaris platform, you always get a hostonly network - that's what vboxnet0 is - so you don't need to create one, and in fact the create option doesn't even exist so it errors out.
The second little patch is that the arguments to SSH don't quite match the SunSSH that comes with illumos, so we need to remove one of the arguments. In the file src/github.com/boot2docker/boot2docker-cli/util.go, look for DefaultSSHArgs and delete the line containing IdentitiesOnly=yes (which is the option SunSSH doesn't recognize).
Then you need to rebuild the project.
env GOPATH=`pwd` go clean github.com/boot2docker/boot2docker-cli
env GOPATH=`pwd` go build github.com/boot2docker/boot2docker-cli
Then you should be able to play around. First, download the base VM image it'll run:
./boot2docker-cli download
Configure VirtualBox
./boot2docker-cli init
Start the VM
./boot2docker-cli up
Log into it
./boot2docker-cli ssh
Once in the VM you can run docker commands (I'm doing it this way at the moment, rather than running a docker client on the host). For example
docker run hello-world
Or,
docker run -d -P --name web nginx
./boot2docker-cli down
While this is interesting, and reasonably functional, certainly to the level of being useful for testing, a sign of the churn in the current container world is that the boot2docker cli is deprecated in favour of Docker Machine, but building that looks to be rather more involved.
