61–63 of 63 posts
So this means DigitalOcean, when running CoreOS via Docker for your deployment, means you no longer need to worry about OS level updates? Is this now handled by DigitalOcean?
Earlier quoted context omitted.
I'm really out of touch with Docker and CoreOS, so please forgive my ignorance if this is a ridiculous Q: could this combo be used for spinning up machines with specific apps for thin clients? Or is it more about scaling one app?
Essentially it lets you run 20 super-lightweight VMs on a single machine... Each one of those could be running different apps, and Docker makes it really easy to build a custom machine image using a single script (called a Dockerfile) using any standard linux OS as a base. So yes, powering 20 thin clients running different apps from a single server is a perfect use case.
What I want is to make groups of containers that can talk only to each other(only to containers within one group). Does CoreOS provide something like that? Maybe kubernetes? What are possible options?
Earlier quoted context omitted.
Essentially it lets you run 20 super-lightweight VMs on a single machine... Each one of those could be running different apps, and Docker makes it really easy to build a custom machine image using a single script (called a Dockerfile) using any standard linux OS as a base. So yes, powering 20 thin clients running different apps from a single server is a perfect use case.
What about isolation between apps? I have app A connected to database A, and app B connected to database B. Is there a way to deny connections from app A to database B etc? What I want is to make groups of containers that can talk only to each other(only to containers within one group). Does CoreOS provide something like that? Maybe kubernetes? What are possible options?