boot2docker

You could configure dockerd (in the VM) to listen on TCP [1][2], then, back in OpenBSD, define & export `DOCKER_HOST` [3] and from then on use the 'docker' client on OpenBSD [4] without even having to ssh into Alpine. Warning: I have not yet tested this yet, but it's about the same way as it works on macOS. Also, I would have probably tried to use boot2docker [5] as guest instead of Alpine. [1] https://docs.docker.com/engine/reference/commandline/dockerd... [2] https://docs.docker.com/engine/security/https/ [3] https://docs.docker.com/engine/reference/commandline/cli/ [4] https://www.freshports.org/sysutils/docker/ (< you probably have to build it yourself) [5] https://github.com/boot2docker/boot2docker

Previously I had permission issues (Only root can write to host) when mounted a folder with OSX filesystem. Hope this would fix those issues. I'm talking about this issue https://github.com/boot2docker/boot2docker/issues/581

It's been a while, but I believe the fix is in this thread: https://github.com/boot2docker/boot2docker/issues/628

Just a quick note after losing a lot of time today with this. VirtualBox (all versions) are having issues starting develop environments under Windows 10 RTM and this is affecting a lot of people who are upgrading to Windows 10. List of relevant VirtualBox dependent projects affected: - vagrant - boot2docker - docker machine - xamarin android player - probably more... Details: - https://www.virtualbox.org/ticket/14040#comment:25 - https://github.com/boot2docker/boot2docker/issues/1015 - https://github.com/mitchellh/vagrant/issues/6059

boot2docker is not connected to Vagrant, it speaks directly with Virtualbox. Maybe watch out in the boot2docker github repo when they gonna update it https://github.com/boot2docker/boot2docker/issues/979 My advice also: Avoid the official docker installation. It will downgrade your Virtualbox 5.0 pretty sure!

It isn't really – this is more akin to Boot2Docker https://github.com/boot2docker/boot2docker. It is a minimal linux install intended for non-native hosts to run Docker containers, say on a Mac or in a VMware cluster. You could use it for production workloads, certainly, but it doesn't provide any of the management tools that CoreOS provides.

From reading the release notes, it looks like the current 1.0.0 release doesn't work with the latest stable docker 1.3.1 due to incompatibilities with the tls layer? https://github.com/deis/deis/releases https://github.com/boot2docker/boot2docker/issues/571 https://github.com/deis/deis/issues/2230 Why not wait until that is resolved before announcing production ready? :-(

Actually, maybe I'm not on 1.3... I did do a "boot2docker upgrade", but when I do "boot2docker version", I'm still getting 1.2.0: (py)cmbpr:~ caleb$ boot2docker upgrade Downloading boot2docker ISO image... Latest release is v1.3.0 Success: downloaded https://github.com/boot2docker/boot2docker/releases/download... to /Users/caleb/.boot2docker/boot2docker.iso Waiting for VM and Docker daemon to start... .............................. Started. Writing /Users/caleb/.docker/boot2docker-vm/ca.pem: Writing /Users/caleb/.docker/boot2docker-vm/cert.pem: Writing /Users/caleb/.docker/boot2docker-vm/key.pem: To connect the Docker client to the Docker daemon, please set: export DOCKER_HOST=tcp://192.168.59.103:2376 export DOCKER_CERT_PATH=/Users/caleb/.docker/boot2docker-vm (py)cmbpr:~ caleb$ boot2docker version Client version: v1.2.0 Git com

There are a lot of non-power users that need Office to get their job done. This limits their options to OS X, Windows, or possibly iOS. The workflow you're describing is pure power-user. There's nothing normal about that. Also Docker on OS X is about as breezy as you can get if you use boot2docker (https://github.com/boot2docker/boot2docker).

If you're using Vagrant, you'll have to manually shut off the VM via `vagrant halt`. If you're just trying to get started with Docker, Boot2Docker (https://github.com/boot2docker/boot2docker) is probably the way to go. If you're looking for an Ubuntu-based Vagrant box, you can try out my Vagrant box (http://ferry.opencore.io/en/latest/install.html#os-x). It's based off of 14.04. Be warned though, my box is very large (~4GB) as it contains many pre-baked images (Hadoop, Cassandra, etc.).

However, Docker is officially supported on OS X through https://github.com/boot2docker/boot2docker

boot2docker[1] is now the recommended environment for docker on osx, but sadly sharing files is not as easy as it is with docker-osx. They just integrated nfs support though [1] https://github.com/boot2docker/boot2docker

Thanks! I solved the issue—it was due to CrashPlan using port 4243 (doh!) https://github.com/steeve/boot2docker/issues/48

Which version of boot2docker are you using? Also, which version of VirtualBox? See also https://github.com/steeve/boot2docker/issues/48 which has some more information about this specific issue.