docker cp: Copy Files In and Out of Containers, and When Not To
By Vladimir Mikhalev · Docker Captain · CNCF Ambassador · IBM Champion
You haven’t lived in DevOps until you’ve had to yank logs out of a container that’s going down in flames. That’s when docker cp becomes your best friend.
Simple. Brutal. Effective.
This guide skips the fluff. I’ll show you how to use docker cp like a pro, with real-world examples, the edge cases nobody mentions, and zero hand-holding. Tired of shelling into containers just to grab a config file? Then this one’s for you.
What docker cp Actually Does
At its core, docker cp lets you copy files to and from containers. No exec. No shell. No drama.
Think of it as the Docker version of scp or cp. The difference is that the “remote” machine is your container’s filesystem.
Syntax
docker cp [OPTIONS] CONTAINER:SRC_PATH DEST_PATHdocker cp [OPTIONS] SRC_PATH CONTAINER:DEST_PATHWant the fine print? Official docs are here.
Real Use Cases (You’ll Actually Run Into)
So when do you reach for docker cp? Here’s where it earns its keep.
1. Quick Debugging
Container misbehaving? Use docker cp to pull logs or config files without needing a shell.
docker cp mycontainer:/var/log/app.log ./app.log2. Saving Critical Data
Back up SQLite DBs, flat files, or anything else that lives inside the container.
docker cp mycontainer:/app/data.db ./backup/data.dbNote: If your app writes to /tmp, don’t be surprised if it disappears after a restart.
3. Hot Config Injection
Update a config file without rebuilding the image or restarting the container:
docker cp ./nginx.conf mycontainer:/etc/nginx/nginx.confdocker exec mycontainer nginx -s reloadExamples That Actually Help
Copy a File Into a Container
docker cp ./local.env mycontainer:/app/.envCopy a File Out of a Container
docker cp mycontainer:/app/logs/output.log ./output.logMove a File Between Containers (No, There’s No Magic)
Docker doesn’t support container-to-container copy directly. So do it the old-school way:
docker cp app1:/data/export.csv /tmp/export.csvdocker cp /tmp/export.csv app2:/import/export.csvFeels clunky? It is. For anything you do often, use volumes.
Gotchas You’ll Run Into (and How to Fix Them)
“permission denied”
docker cp won’t magically override file permissions. Copy something into /root while your container app runs as node, and guess what? It’s not going to work.
Use bind mounts, or fix permissions after the copy:
docker exec mycontainer chown node:node /app/.envPath Doesn’t Exist
Screw up the target path, say by copying into a directory that isn’t there, and Docker will not helpfully create it for you. It’ll fail. As it should.
When docker cp is the Wrong Tool
- Doing frequent file syncs? Use bind mounts.
- Need data persistence? Use Docker volumes.
- Want to avoid weird race conditions with scripts reading partially-copied files? Don’t use
docker cpmid-execution.
Example: bind mount your code during dev:
docker run -v $PWD:/app myimageThat way, edits on the host show up inside the container the instant you save.
More on Docker volumes here.
Final Thoughts
docker cp is like a crowbar. Not elegant. Not subtle. But when you need to pry data out of a sealed container, nothing beats it.
Use it for:
- One-off debugging
- Quick backups
- Emergency surgery on broken containers
Don’t build your whole deployment process around it, though. For that, reach for volumes and proper orchestration, and stop pretending docker cp is a deployment strategy.
Pro tip: Set an alias. You’ll thank yourself at 3AM.
alias dcp='docker cp'Want to go deeper on Docker CLI workflows or file sync strategies? Ping me, or check out the official Docker docs.