3 ms·
A workaround for this is to run Docker Engine inside a (non-Docker) container and use that container's socket. The Docker containers become processes within the
by dharmab 3y ago
A workaround for this is to run Docker Engine inside a (non-Docker) container and use that container's socket. The Docker containers become processes within the Docker Engine container.
- remram 3y agoAFAIK you can't do that without giving the Docker-in-Docker container privileged permissions, which allows escaping.
- dharmab 3y agoYou can do what Docker Desktop does- put the whole thing in a VM :^) You still can't run untrusted code but at least you can isolate stuff like Compose environments