3 ms·
Absolutely, one of the things I find very frustrating about Docker is that for the situations I need it it's never sufficient in itself, you still need to be ma
by Traster 7y ago
Absolutely, one of the things I find very frustrating about Docker is that for the situations I need it it's never sufficient in itself, you still need to be mapping ports and volumes and setting variables- and that's all done in terminal commands which I have to remember or store somewhere and if I get something wrong it all falls apart. With docker-compose I've actually got a single file that I an use to make sure the container actually is reproducible. I'm willing to accept that maybe I just have weird requirements though.
- cmehdy 7y agoI'm definitely not arguing about the advantages that docker-compose can bring (for me: readability & multiple containers easily connected), but aren't port mapping (-p) and env. variables (-e) and volumes (-v) simple with a docker command? See https://docs.docker.com/engine/reference/commandline/run/ https://docs.docker.com/engine/reference/commandline/run/
- Traster 7y agoThey're simple, but what I want is a file I can point to and say "This is how we do things", to me that's a large part of what docker-compose brings.