4 ms·
In production, you usually don't want to have users running around and spawning containers anyway. You will likely have an orchestrator like Kubernetes or Mesos
by majewsky 10y ago
In production, you usually don't want to have users running around and spawning containers anyway. You will likely have an orchestrator like Kubernetes or Mesos or Swarm, who will be running as root and spawning containers for you.
Of course, that just replaces the question of "how is access to the docker daemon secured?" with "how is access to the orchestrator API secured?".
- shriphani 10y agoHow about something that isn't spawned by an orchestrator - for instance the marathon load-balancer - they provide only a docker image which clearly is meant to be run using `docker run`
- majewsky 10y agoI would still run it using an orchestrator, if only to have it restart the container automatically on failure or after your node reboots.
- shriphani 10y agoI mentioned this in a sibling comment - I'm currently running the container using systemd which gives me restart ability and all that. Do you think this is insufficient?