At my day job
, all our production servers are deployed as Docker containers on a Kubernetes cluster. So sounds like we need to know Docker, right?
Turns out you don’t. Our most recent software job listing
doesn’t list Docker or Kubernetes. Even as a staff-level engineer who occasionally does some devops-like work, I didn’t have Docker installed on my machine for 3 years. I installed it a couple weeks ago… for a workshop.
In my experience, the day-to-day of being a Node.js developer involves very little direct Docker usage. Unless I’m testing, our CI handles running `docker build` and pushing our images.
The most common use case I’ve seen for running Docker locally is Docker Compose
, which is a neat tool for running multiple projects at once. If you need to start up 4 different REST APIs to power your frontend, it may be handy for you to have a docker-compose file that starts up all 4 on the right ports with a single command.
But you can always work around the need for docker-compose by starting the API servers yourself. If you want to avoid using Docker, you usually can avoid using Docker.
TLDR; read this blog post