dockly

Immersive terminal interface for managing docker containers and services

Runs with mockssource: GitHubhomepageJavaScriptMITcommit 572698cbcb5c

JavaScript, MIT licensed. The project labels itself: cli, command line tool, console, containers, docker, hacktoberfest and nodejs.

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

npm install completed, lint passes, app loads its version/help screens on command and launched its full terminal UI against a mock Docker socket and stayed alive for 15 seconds without crashing.

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
2
last tested
stars
4,037
forks
162
open issues
3
watchers
41
size
7 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 dockly, 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.

  • No Docker available in container - app requires Docker daemon for full functionality.1 minute
  • Original .npmrc had engine-strict=true which blocked npm install on Node v18 (required: >=24). Also had min-release-age=30 and allow-git=none which would block new packages.0.5 minutes
Install time
2 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm test (lint + lockfile-lint) exited 0 with no issues; node index.js --version printed 'dockly 0.0.0-development by Liran Tal...' (exit 0); node index.js --help printed all CLI options (exit 0); node index.js -s /tmp/mock-docker.sock launched the TUI and stayed alive for 15 seconds until timeout (exit 124 = timeout, meaning no crash)
Model tokens used
123,608
Exact commit tested
572698cbcb5c
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.

EOF
echo \"done\"" in /work/repo
 succeeded in 0ms:
done
Now let me kill the background mock server:
exec
/bin/sh -lc 'pkill -f "node /tmp/mock-docker.js" 2>/dev/null; true' in /work/repo
 exited 143 in 0ms:
Everything is in order. Let me compile the final report.
tokens used
123,608
Everything is in order. Let me compile the final report.

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

  • Installed in 2 minutes, faster than the median of the 123 comparable projects Argusic has measured.
  • Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, 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.

Of the 124 cli projects Argusic has installed and timed, dockly was the 37th fastest to reach a running state, and 112 of 124 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.05
Argusic Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

clicommand-line-toolconsolecontainersdockerhacktoberfestnodejs

Embed the badge

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

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

Questions

Does dockly run?
dockly runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test dockly?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 572698cbcb5c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test dockly?
The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does dockly take to install?
2 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 dockly need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing dockly?
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 dockly compare with the alternatives?
Of the 124 cli projects Argusic has installed and timed, dockly was the 37th fastest to reach a running state, and 112 of 124 reached one at all.
Where is the evidence for dockly?
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