That depends on the runtime that the containers are using. At my company we explicitly do not consider docker + runc as a security boundary due to the shared Li

That depends on the runtime that the containers are using. At my company we explicitly do not consider docker + runc as a security boundary due to the shared Linux kernel - but you can hedge against this with technology like gvisor, or executing via kvm + firecracker containers (kata containers do this iirc), etc. So it's less about "docker" and more about the container runtime. They could also be leveraging seccomp or some other mechanism. It's unclear in this case if they're relying on just default Docker. If they are, that's concerning to me. They do mention apparmor, gotta dig in more. This also relies on a path traversal, so it may be reasonable.