Docker · Practical guide
‘It worked on my laptop’ is a bad launch plan.
Why Docker helps a small team keep a custom tool repeatable.
A note from the studio
A developer builds a small scheduling tool and it works perfectly on their computer. Then it moves to the server and a missing package breaks it. That is the sort of problem Docker is meant to reduce.
Featured podcast / The Deeper DiveThe developer is on vacationWatch the illustrated story or listen after the guide
The box is the point
Docker packages an application and the pieces it needs into an image. A container runs that image. The idea is that the same version can be tested, handed to another developer, and run in hosting without rebuilding the setup from memory. Docker Compose can describe several connected parts, such as an app and a database, for local development.
For a small business, this is mostly invisible, and that is fine. You should care when it makes a handoff or recovery easier. If your only developer is away, another person should be able to see what runs the tool and start a known version without digging through a laptop full of private setup notes.
A container is not the whole system
Docker will not write backups, check whether a customer request reached the office, or keep a secret safe by itself. Data needs deliberate storage. Updates need a test and a way back. Ask your developer to show you the run instructions and the recovery plan in plain English.
When the original developer is away, someone else can start the tool and find the appointments. That is the handoff worth paying for.
A practical first step
What we would put in place
- Package the custom app and its setup.
- Ask a second developer to start a clean copy.
- Write down data, secrets, backup, and rollback steps.
Starting tool cost
$0 for eligible small businessesDocker Personal/Desktop is free when the business has fewer than 250 employees and under $10 million in annual revenue. Hosting and developer time are separate.
Check Docker Personal terms USD, checked September 25, 2026. Tool fees are separate from design, development, and ongoing care. See how Mata.Works quotes the build and care.Featured podcast / The Deeper Dive
The developer is on vacation
A second developer needs to run the scheduling tool. Docker can help, but the handoff needs more than an image.
Read the episode transcript
AI voices perform a script reviewed by Mata.Works. Landon and Tam are the illustrated hosts. The business scenario is an example.
Landon: The person who built a scheduling tool takes a week off. On Tuesday it stops working. The office calls a second developer, who says, "I can't even start it on my computer."
Tam: That is a handoff problem. Docker can package the application and the software it needs so another developer can run the same setup. It takes a lot of "works on my laptop" out of the conversation.
Landon: Does it package the schedule and customer records too?
Tam: Usually those live somewhere else, and they should. The second developer needs to know where the data lives, how the app connects to it, where credentials are kept, and how to restore service. A container alone will not answer any of those questions.
Landon: If I own the business, what do I ask for before the first developer goes on vacation?
Tam: Ask someone who did not build the tool to start a clean copy from the written instructions. Then have them make a test booking. Can they find a failed request? Do they know whom to call if the database is down? Can they put the previous version back if a change breaks the app?
Landon: That sounds like a rehearsal, not a binder that nobody opens.
Tam: Exactly. If the handoff fails, write down the missing step and try again. Keep the instructions with the code. The goal is for another capable person to recover the tool without guessing at the original developer's laptop.
Landon: When would you skip Docker?
Tam: If the business uses an off-the-shelf scheduling service that already meets the need, there may be no custom app to package. Use the smallest setup that another person can operate. Docker earns its place when it makes a custom tool easier to move, test, and repair.
Landon: So the owner is buying continuity.
Tam: Right. The test is whether Tuesday's appointments still work when the original developer is unavailable.
Would this fix a real snag at your shop?
Make the tool easier to hand off