3 ms·
Agreed. I was worried docker-compose might be abandoned for swarm-only at the kubernetes level. Compose is a much easier level to develop and work with. Doesn't
by daveguy 7y ago
Agreed. I was worried docker-compose might be abandoned for swarm-only at the kubernetes level. Compose is a much easier level to develop and work with. Doesn't do all the balancing and HA, but for most projects you don't need that, just good organization of the pieces.
- kalev 7y agoThis is exactly why we still use compose as well. Everybody is talking about kubernetes, but I honestly don’t see the point in adding a huge dependency only for balancing and restarting failed containers.. I just wish there was some SaaS platform which allows you to upload a docker-compose file and run the containers for you. That way, you don’t have to touch the underlying OS.
- larrybud 7y agoAzure App service lets you do this. https://docs.microsoft.com/en-us/azure/app-service/containers/quickstart-multi-container https://docs.microsoft.com/en-us/azure/app-service/container...
- tilolebo 7y agoThe AWS ECS cli has this kind of feature (I never used it) : https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cmd-ecs-cli-compose.html https://docs.aws.amazon.com/AmazonECS/latest/developerguide/... v2 even allows to create the underlying networking resources (VPC), provision an application load balancer, etc.
- jswny 7y agoAren't Compose and Swarm/Stack very similar, but Stack has support for distribution between multiple nodes? I know their actual configurations aren't equivalent, but they are similar (Stack supports config options for distribution, etc.).