docker-vackup

Script to easily backup and restore docker volumes

Not yet testedsource: GitHubShellUnlicensecommit 6b8a06f6cb4f

Shell, Unlicense licensed. The project labels itself: backup, containers, docker and volumes.

docker-vackup has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
493
forks
79
open issues
1
watchers
9
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

  • moby verified to run · Go · 2 shared topics
  • witr verified to run · Go · 2 shared topics
  • docker-volume-backup verified to run · Go · 2 shared topics
  • portabase verified to run · TypeScript · 2 shared topics
  • watchstate verified to run · PHP · 2 shared topics
  • tugtainer verified to run · Python · 2 shared topics

Run history

No recorded runs.

Topics (from GitHub)

backupcontainersdockervolumes

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/docker-vackup.svg)](https://argusic.com/subject/docker-vackup)

Questions

Does docker-vackup run?
docker-vackup has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test docker-vackup?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for docker-vackup?
All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion