6 ms·
> Am I just totally wrong here? Yes. I think so. docker-compose is just a tool to run multiple containers together. It is extremely simple, readable and strai
by avip 7y ago
> Am I just totally wrong here?
Yes. I think so.
docker-compose is just a tool to run multiple containers together. It is extremely simple, readable and straightforward (if you're familiar with docker). It is not an inf. abstraction at all.
- stevebmark 7y agoIt's not extremely simple. Do you know when to use v2 vs v3?
- williamdclt 7y agoLooking into it for a minute I don't see any particular gotcha. v3 is a breaking change compatible with Docker Swarm, so it's just like any versionned tool: if you're already on v2 and don't care about the new feature stay there, if you're on a greenfield project or do care about new feature use v3. Am I missing something?
- deleted 7y ago[deleted]
- avip 7y agoIt's like asking when to use python2. Use v2 if you have no choice. If you're asking, apparently you have the choice, so there's your answer.
- stevebmark 7y agoNope, entirely wrong! v3 isn't an upgrade, it has features specific to orchestration. v3 is a fork, not an upgrade. v2 is better for local development, it has things like depends_on which v3 doesn't have.
- avip 7y agodepends_on was removed because it was an inconsistent and problematic directive. You can abuse links instead.
- stevebmark 6y agoYou should only use v3 if you need v3 features and know how to use them. You should use v2 for local development if you're not using stack/swarm locally: https://github.com/docker/compose/issues/4305#issuecomment-305378202 https://github.com/docker/compose/issues/4305#issuecomment-3...