Comment by nickstinemates | Hacker News Reader

Comment by nickstinemates | Hacker News Reader

Parent Full thread

I think the UX is slightly more nuanced.

From any machine, you should be able to `docker run` any application, and docker will be smart enough to find (or create!) the best place run it.

The base pieces of the lego are currently in flight in Docker proper to enable this, with great tools built around the Docker API for more advanced topics (like clustering and scheduling)

> Running boot2docker on windows is sort of cheating in that it is a virtual machine running docker apps and this effort appears to be a native dockerd running on Windows.

I wouldn't say it's cheating. If your target is all linux machines, you need a cheap, local, efficient way of developing and testing those applications. Boot2Docker is an option (but not the only one - you could use a cloud service, internal vm infra, etc. etc.)

Love the dialogue - keep it coming.

Ok so I read that as you saying:

If you're running docker on windows and you try to run a linux container, it will magically start boot2docker and start your linux container inside that vm if you are running on a windows box.

Now if that is true, my question would be: How do you boot2windows for windows docker images when you can't freely distribute a windows vm?

As I think both being able to support both would be amazing, I don't see how it fits into the current scheme of things.

> If you're running docker on windows and you try to run a linux container, it will magically start boot2docker and start your linux container inside that vm if you are running on a windows box.

Maybe! Or you've used something like the new `docker hosts` feature, which could create a new instance for you on any infrastructure provider. Or you could be pointing to a boot2docker node, etc.

> Now if that is true, my question would be: How do you boot2windows for windows docker images when you can't freely distribute a windows vm?

I don't have a good answer for this, as we do not have a boot2windows product or announcement (I assume this is the opposite case, if you have a linux machine and want to run a windows image)

My guess instead is you'd be pointing to a set of infrastructure that can find (or create) Windows Docker Hosts and it would run there.

I'm excited to see what the future brings! Can't wait to see some of the service discovery stuff like you can build with etcd and consul make it into libswarm.

Not libswarm, docker proper.

See https://github.com/bfirsh/docker/tree/host-management

There's also a relevant thread on the docker-dev mailing list

Reply on news.ycombinator.com