I’m experiencing an issue running Windows containers on Docker Desktop for Windows. My primary container needs internet access, so I launch it without the --network none option. However, this container then spawns a secondary container using docker run --network none to restrict internet access for the binaries within.
The secondary container runs successfully, but when it exits, it crashes the primary container and causes Docker Desktop to crash completely. Removing the --network none option from the secondary container resolves the issue, but this is not the desired behavior.
Has anyone else encountered this problem or have insights into why using --network none with nested Windows containers might lead to this cascading crash?
Also, We have a similar container image for linux, and we have not experience issue there.