ue4-docker

Windows and Linux containers for Unreal Engine 4

Runs with mockssource: GitHubhomepagePythonMITcommit 7f1eccc538b3

Python, MIT licensed. The project labels itself: continuous integration, docker, ue4 and unreal engine.

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

ue4-docker 0.0.124 is installed in a Python venv at /work/repo/venv; all package imports succeed; CLI 'version', 'info', 'diagnostics all' (4/4 passed), 'setup', 'clean' and 'build --dry-run' (generates 27 docker build commands for UE 5.4) all work against a mock Docker API; real Docker image builds require a Docker daemon which is not available in this container.

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.07 (measured)
recorded runs
2
last tested
stars
840
forks
177
open issues
34
watchers
29
size
1 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 ue4-docker, 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 daemon not installed in container8 minutes
  • setup command failed looking for docker binary in PATH1 minute
  • Ubuntu 24.04 externally-managed Python environment blocks system pip install0.5 minutes
  • info command failed because mock DockerRootDir /var/lib/docker didn't exist0.5 minutes
Install time
under a minute
Cold machine to finish
16 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
DOCKER_HOST=tcp://127.0.0.1:12375 PATH=/tmp/fakebin:$PATH /work/repo/venv/bin/python -m ue4docker version printed '0.0.124'; 'ue4-docker info' printed all fields correctly; 'ue4-docker diagnostics all' passed all 4 diagnostics; 'ue4-docker build --dry-run --rebuild --ue-version 5.4.4 --target all' generated 27 docker build commands; layout generation produced /tmp/ue4layout_final/generated.json; test suite dry-run printed all 15 expected commands across 7 UE releases
Model tokens used
478,355
Exact commit tested
7f1eccc538b3
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

usage: python -m ue4docker clean [-h] [-tag TAG] [--source] [--all]
                                 [--dry-run] [--prune]
--- 9. Setup ---
No firewall configuration required.
--- 10. Test suite dry-run ---
['/work/repo/venv/bin/python', '-m', 'pip', 'install', '--user', '/work/repo']
['/work/repo/venv/bin/python', '-m', 'ue4docker', 'build', '--ue-version', 'custom:4.27', '-repo', …
['/work/repo/venv/bin/python', '-m', 'ue4docker', 'clean', '-tag', '4.27', '--all', '--prune', '--d…
Here's the final comprehensive report:
tokens used
478,355
Here's the final comprehensive 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 0.1 minutes, faster than the median of the 3 comparable projects Argusic has measured.
  • Recovered from all 4 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 4 continuous-integration projects Argusic has installed and timed, ue4-docker was the 1st fastest to reach a running state, and 1 of 4 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/3Runs with mocks92.000.18

Topics (from GitHub)

continuous-integrationdockerue4unreal-engine

Embed the badge

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

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

Questions

Does ue4-docker run?
ue4-docker runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test ue4-docker?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7f1eccc538b3. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ue4-docker?
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 ue4-docker take to install?
0.1 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 ue4-docker need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ue4-docker?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does ue4-docker compare with the alternatives?
Of the 4 continuous-integration projects Argusic has installed and timed, ue4-docker was the 1st fastest to reach a running state, and 1 of 4 reached one at all.
Where is the evidence for ue4-docker?
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