What is Docker?
Corbin Brown
2 min read
Part of the Vibe Coding Fundamentals video series on YouTube.
Software is fussy about its surroundings. An app that runs perfectly on your laptop can fail on a server because the server has a different version of some tool, a missing dependency, a different operating system. Docker's fix: stop shipping the app, ship the whole kitchen. A container packs your app together with everything it needs (exact versions, settings, supporting tools) into one sealed box that runs identically anywhere Docker runs.
The shipping container analogy (it's in the name)
Before shipping containers, moving goods between a truck, a crane, and a ship meant repacking at every step. The standardized container ended that: pack once, and every truck, crane, and ship in the world can handle it without looking inside. Docker did that for software. Your laptop, a teammate's machine, and a cloud server all “handle the container” the same way, so the app inside behaves the same in all three places.
A container differs from a virtual machine in weight: a VM packs an entire fake computer, operating system included; a container shares your machine's core and packs only what the app needs. Containers start in about a second and you can run dozens without your laptop melting.
How much of this do you actually need?
For most vibe-coded web apps: less than the internet suggests. Platforms like Vercel, Replit, and Lovable containerize behind the scenes precisely so you don't have to. Docker enters your life in three realistic ways: an agent suggests it to run a database locally (reasonable: one command instead of an installation saga), a project's README says “run with docker compose up” (that command starts the app and everything it needs, defined in a file), or you deploy somewhere that expects a container image. In all three cases the agent writes the Docker configuration; your job is the concept, not the syntax.
FAQ
Do I need Docker to vibe code?
No. If your agent hasn't brought it up, you don't need it. It becomes worth learning when you self-host, need a local database, or join a project that already uses it.
What's a Dockerfile?
The packing list: a text file describing how to build your container: start from this base, copy the code in, install these dependencies, run this command. Agents write good ones; ask yours to explain each line once and the mystique evaporates.