|
|
|
|
|
by LethargicStud
2431 days ago
|
|
This is the exact class of problem that docker itself attempts to avoid. This is why I run docker-compose inside a docker container, so I can control exactly what it has access to and isolate it. There's a guide to do so here[1]. It has the added benefit of not making users install docker-compose itself - the only project requirement remains docker. 1: https://cloud.google.com/community/tutorials/docker-compose-... |
|
Do you use Docker-in-Docker or do you mount the docker socket inside your docker-compose container?
Oh dear god .. it's Docker all the way down.