[atemerev]

You have to learn it — where? Documentation is sketchy and mostly obsolete, docker-swarm is buggy, genuine production issues are routinely closed with WONTFIX resolution.

Could you point me to good piece of documentation or success story of running Docker in production?

(I do use Docker, but it requires to learn Kubernetes or DCOS to do anything production-related. And those are separate projects).

[fireflash38]

Every one of these blog posts begins with almost exactly the same thing:

The documentation just plain sucks. The doc parts that don't suck are outdated, and therefore useless.

As long as that is the case, you are going to have people who go through the exact same troubles with Docker time and time again (one theme is databases in docker).

[cpuguy83]

Maintainer here, can you please point to a production issue that is WONTFIX?

[atemerev]

(Transferring ~/.docker wasn't an option as I already had a set of my own hosts on my computer, and manually editing undocumented configuration files is harder than it sounds — for some reason I forgot, I couldn't partially transfer some hosts but not the other. This is after I have spent 2 days in even deciphering what has happened, as error messages are uninformative and Docker CLI just hangs in an endless loop in such situation).

Nothing of it is documented, of course.

[cpuguy83]

Indeed, would definitely be cool to be able to export a specific machine config to a tarball that can be imported on another machine. I don't work on machine, but anyone made a proposal for this (probably with warnings about copying ssh keys and such)?

I know this doesn't help with your current issue on docker-machine, but... I think the issue here is docker-machine's primary intent is as a developer tool to spin up dev environments quickly and easily (zero-to-docker as we say), as such the datastore and security model is tailored to this. We are working on production-level infrastructure management, the base-layer of which you can find here: https://github.com/docker/infrakit

[atemerev]

Docker-swarm is positioned as a production-grade orchestration tool, yet it depends on docker-machine. :(

[cpuguy83]

Why do you say it depends on docker-machine?

[atemerev]

This one: https://github.com/docker/machine/issues/3212

In essence, it is impossible to work with an existing Docker-managed host from another computer. I often work from home, and when I wanted to manage my Docker hosts from my laptop, it turned out to be impossible and this issue was closed without resolution.

This was the day when I gave up on using native Docker.

[atemerev]

On docker-machine: https://docs.docker.com/swarm/provision-with-machine/

(Or, how else should I provision Docker on multiple non-AWS hosts at once?)

[cpuguy83]

(Classic) Swarm is just a service like any other. You can deploy it with `docker run`, which is what machine is doing for you.