4 ms·
I don't think that's really a docker problem. Its more about the instances of software that you want to run together. e.g. nginx in isolation is useless. But i
by wdfx 3y ago
I don't think that's really a docker problem. Its more about the instances of software that you want to run together.
e.g. nginx in isolation is useless. But is really useful when you want to expose a bunch of other services on a single http(s) interface.
When you are working at the compose level you are thinking about an ecosystem of services working together and of course then you are you using the compose tools to achieve that. But managing each component in isolation is much more tedious.
- Ajedi32 3y agoEven with only one service I still consider Compose to be a necessity. Otherwise you need to manually specify how to mount the volumes, set the environment variables, and forward ports when you run the container. Only the most trivial containers are easily usable with plain `docker run`.
- wdfx 3y agoThat's a fair point I suppose that docker itself doesn't provide a declarative config for starting containers. But that is also true of a whole bunch of tools which only either provide cli or config but not both
- yownie 3y agoyes all of which results in extremely poor end user experience. I'm glad we're in agreement here.
- aquova 3y agoI agree. Having containers start at boot automatically is a useful enough feature to make compose worth it.