Needs a new backup system
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The proposal is for new docker backup --all and docker restore --all commands in the Docker CLI. Start by locating the CLI entry points and existing volume or archive handling, then define portability and recovery requirements; done should include a usable backup and restore flow, with tests covering the supported data.
Written by the indexing model from the issue text.
Description
Description
The backup system in docker is the worst most garbage backup system I've ever seen in my 25 years of living and in any software. I spent over 5 ****** hours trying to recover MY data, have about 11+ years of experience in IT and many years with self-hosted apps in docker can't because the backup system in Docker is unusable.
Basically you store anything in a docker volume, just assume it can never be reached again except for that exact computer. Someone spends hours of their life self-hosting something they need for day to day work and their computer dies? Screwed out of all that date, If this were an enterprise that needs uptime it would be billions of dollars lost over bad programming.
I tried copying /var/lib/docker but that doesn't work for some magic reason. I did exact copy with rsync, exact permissions and even factoring in ACLs and any minute little thing, nope. Don't work. How is this even possible? How can a program just not at all recognize the exact data on another computer unless it's deliberately coded to frustrate the end user.
Here is how it should work:
docker backup --all
Then it just makes a zip file, then to restore:
docker restore --all
Whoever made this system needs to fire them immediately they are an active hindrance to your project. Multi billion dollar enterprises are losing time and money on this joke of a system and they should be fired immediately.
Reproduce
.
Expected behavior
No response
docker version
.
docker info
.
Additional Info
No response
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/cli
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
kind/feature status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
kind/bug status/0-triage
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NVIDIA/gpu-operator#2955 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cisagov/vulnrichment#337 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100