* Yes, we will start gpg-signing our binaries. We are going to sign our git tags while we're at it. If you really can't download a binary from a trusted domain to execute as non-root on your laptop, here are the build instructions: http://docs.docker.io/en/latest/contributing/devenvironment/
* Since this has been submitted, 0.7.3 has been promoted to a stable release.
* This does not allow docker to natively run containers on a mac (although we're also working on that :). This allows using docker in client mode from the mac, to interact with a remote docker daemon, either on a local VM or another machine. You can control which daemon to connect to with the -H flag, or by setting the $DOCKER_HOST environment variable.
* The perfect companion for this is boot2docker: http://github.com/steeve/boot2docker. It's a 25MB VM which boots to a functional docker daemon in less than 5 seconds.
* This is only the beginning of our support for OSX as a target platform. the boot2docker and docker-osx folks are collaborating to bundle all of the above together in a single, ready-to-use mac installer. As soon as they do, we will merge it upstream as the official mac installer.
* Respectfully to the author of Vagrant who commented below: with docker + boot2docker, I basically don't need Vagrant anymore. I'm glad existing Vagrant users can benefit from a subset of docker's features without losing their existing Vagrant setup. But if you're starting fresh, use one or the other - not both.
FWIW, boot2docker became my favorite all-purpose, ready-to-run, ridiculously-small-and-therefore-insanely-fast-to-download VM image.
It's faster to download it (it's 25 MB) and start it with qemu, than to go through the clicky-pointy interfaces of VirtualBox etc., or go through the download of a full Vagrant box. This is game changing.
With a single installer on Mac which will bring both, boot2docker and native Docker client, we have a fully functional Headless Hypervisor!
Next step is Windows?
If you're looking for a dev-oriented Solution, consider Docket. Configure your c build scripts, containers and docket configs and commit them to a Git repository.
https://github.com/polydawn/docket
Unfortunately, the documentation refers to the local docket install as a cache though the containers are persistent as any docket container is.
So how do I get the client going? You linked to the release but there is no documentation on building or running the osx client. Am I missing something? Maybe I am too late to the party.
* Yes, we will start gpg-signing our binaries. We are going to sign our git tags while we're at it. If you really can't download a binary from a trusted domain to execute as non-root on your laptop, here are the build instructions: http://docs.docker.io/en/latest/contributing/devenvironment/
* Since this has been submitted, 0.7.3 has been promoted to a stable release.
* This does not allow docker to natively run containers on a mac (although we're also working on that :). This allows using docker in client mode from the mac, to interact with a remote docker daemon, either on a local VM or another machine. You can control which daemon to connect to with the -H flag, or by setting the $DOCKER_HOST environment variable.
* The perfect companion for this is boot2docker: http://github.com/steeve/boot2docker. It's a 25MB VM which boots to a functional docker daemon in less than 5 seconds.
* This is only the beginning of our support for OSX as a target platform. the boot2docker and docker-osx folks are collaborating to bundle all of the above together in a single, ready-to-use mac installer. As soon as they do, we will merge it upstream as the official mac installer.
* Respectfully to the author of Vagrant who commented below: with docker + boot2docker, I basically don't need Vagrant anymore. I'm glad existing Vagrant users can benefit from a subset of docker's features without losing their existing Vagrant setup. But if you're starting fresh, use one or the other - not both.