What docker promises is truly amazing and is something that I think everyone wants. However, docker itself still has a lot of problems.
In particular, docker's new builtin swarm (with 1.12) has tons of issues. I've experienced __so many__ problems coordinating container startups on a swarm cluster.
From the documentation:
> Swarm can build an image from a Dockerfile just like a
single-host Docker instance can, but the resulting image
will only live on a single node and won’t be distributed
to other nodes.
This is a serious weakness.
You have to use __manual scheduling__ if you want to ensure services are started on the same node. This is problematic if your inventory of nodes is dynamic and frequently changing. Allegedly, kubernetes solves this problem.
Swarm (and the whole ecosystem) is still not as mature as it could be, but I think the end result is going to be very awesome and useful.
That's probobly a bad pattern to use the local registry like that. The goal is to be as stateless as possible, so pushing and pulling from an external registry would fix that.
What docker promises is truly amazing and is something that I think everyone wants. However, docker itself still has a lot of problems.
In particular, docker's new builtin swarm (with 1.12) has tons of issues. I've experienced __so many__ problems coordinating container startups on a swarm cluster.
From the documentation:
This is a serious weakness.You have to use __manual scheduling__ if you want to ensure services are started on the same node. This is problematic if your inventory of nodes is dynamic and frequently changing. Allegedly, kubernetes solves this problem.
Swarm (and the whole ecosystem) is still not as mature as it could be, but I think the end result is going to be very awesome and useful.