docker-vackup

Script to easily backup and restore docker volumes

Runs with mockssource: GitHubShellUnlicensecommit 6b8a06f6cb4f

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

docker-vackup runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

vackup bash script is executable, bats 1.13.0 installed locally, Python mock Docker CLI handles all docker commands used by vackup (volume create/inspect/ls/rm, image inspect/ls/rm, ps, commit, container rm, run with -v/-e/--rm flags and tar/cp operations), and all 14 test cases in test/vackup.bats pass consistently

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 86 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
86 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
494
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.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing docker-vackup, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Docker CLI not available in container12 minutes
  • bats test framework not installed system-wide (no root)1 minute
Install time
18 minutes
Cold machine to finish
25 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
ALL 14 bats tests passed: cd /work/repo && ./node_modules/.bin/bats test/vackup.bats exited 0 with 14/14 ok; also ran vackup export/import/save/load directly with mock docker and verified output files
Model tokens used
1,153,194
Exact commit tested
6b8a06f6cb4f
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Here's the final report:
**ARGUSIC_RESULT**
```json
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 18, "errors": [{"msg": "Do…
```
tokens used
1,153,194
Here's the final report:
**ARGUSIC_RESULT**
```json
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 18, "errors": [{"msg": "Do…
```

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Unlicense, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 18 minutes to install, slower than the median of the 47 comparable projects Argusic has measured.

Of the 48 backup projects Argusic has installed and timed, docker-vackup was the 44th fastest to reach a running state, and 32 of 48 reached one at all.

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.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.07
Argusic Runner1/3Unverified80.000.11

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 runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test docker-vackup?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6b8a06f6cb4f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test docker-vackup?
The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does docker-vackup take to install?
18 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does docker-vackup need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing docker-vackup?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does docker-vackup compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, docker-vackup was the 44th fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for docker-vackup?
All 2 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