4 ms·
Docker is not for production (most of the time), it's a dev tool. Ignore docker compose (and swarm and whatever else), because you don't need it. The basic Doc
by mozey 6y ago
Docker is not for production (most of the time), it's a dev tool.
Ignore docker compose (and swarm and whatever else), because you don't need it. The basic Dockerfile format is simple, it reads like a bash script without logic, basically it's a list of dependencies. Then you need to understand the difference between images and containers, and you're good to go.
If you're lucky enough to be developing on Linux, then docker is just a name for a bunch of stuff that's mostly already built into the OS.
- tapirl 6y agoI use docker compose only. It is much more convenient than vanilla docker.
- kspacewalk2 6y ago> Docker is not for production (most of the time), it's a dev tool. Sure. >Ignore docker compose Don't ignore Docker compose. It allows you to set up a test/dev environment with dependencies between containers, shared variables/volumes, etc. >If you're lucky enough to be developing on Linux, then docker is just a name for a bunch of stuff that's mostly already built into the OS. We could all just use cgroups to achieve containerization, but why? Docker is a great tool with a huge ecosystem of images at your fingertips, mature and powerful command-line interface, and lots of documentation/googlable discussions for even the most esoteric problems. But yeah, I wouldn't use it in production.
- mozey 6y ago> dependencies between containers This is the part I don't understand. I use Docker as a light weight alternative to say VMWare or Virtual Box, just Dockerfiles work well for this use case. The point is to not have dependencies
- tasubotadas 6y agoSorry, but the stuff you just said is bullshit. Any Docker user will hopefully see that.