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 13.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.
Dockly installs, lints pass, --version and --help work, and the full TUI initializes against a mock Docker daemon with all dockerode API calls responding correctly.
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
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Docker daemon socket available in container5 minutes
- Node.js version mismatch: package.json requires >=24.0.0 but container has v18.19.11 minute
- Install time
- 13 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- npm test exited 0 (lint + lockfile-lint both passed); node index.js --version printed 'dockly 0.0.0-development'; 'dockerode ping/listContainers/listImages/systemDf/getInfo all returned correct data against mock socket' verified via inline node script; 'screen.init() returned without error with mock socket' verified via inline node script
- Model tokens used
- 59,817
- 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.
npm warn Unknown env config "metrics-registry". This will stop working in the next major version of… npm warn Unknown env config "globalignorefile". This will stop working in the next major version of… > [email protected] lint > standard && npm run lint:lockfile npm warn cli npm v11.15.0 does not support Node.js v18.19.1. This version of npm supports the follo… npm warn Unknown env config "metrics-registry". This will stop working in the next major version of… npm warn Unknown env config "globalignorefile". This will stop working in the next major version of… > [email protected] lint:lockfile > lockfile-lint --path package-lock.json --type npm --validate-https --allowed-hosts npm ✔ No issues detected tokens used 59,817
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 MIT, as reported by its host.
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 13.2 minutes to install, slower than the median of the 27 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 28 cli projects Argusic has installed and timed, dockly was the 26th fastest to reach a running state, and 25 of 28 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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Topics (from GitHub)
clicommand-line-toolconsolecontainersdockerhacktoberfestnodejs
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](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 13 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. One attempt is 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.03: 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?
- 13.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 28 cli projects Argusic has installed and timed, dockly was the 26th fastest to reach a running state, and 25 of 28 reached one at all.
- Where is the evidence for dockly?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.