> AFAIK, you can’t spin up containers that might be needed in tests, severely limiting its usefulness.
This is what's blocking me right now. I couldn't find any documentation on whether they allow Docker-in-Docker which typically means that the answer is "no". Since I'm building an AWS-native app I use LocalStack for end-to-end tests which requires a container engine. Codex not having it is a showstopper.
This might not help you but to the very best of my knowledge localstack can operate over the network just fine and I am pretty sure it has a reset endpoint for zeroing its state (I think it's this https://github.com/localstack/localstack/blob/v4.4.0/localst... )
The other alternative is that I've seen folks mention systemd-nsspawn as a form of isolation if that's what your using docker for (but I've never tried it myself)
This is what's blocking me right now. I couldn't find any documentation on whether they allow Docker-in-Docker which typically means that the answer is "no". Since I'm building an AWS-native app I use LocalStack for end-to-end tests which requires a container engine. Codex not having it is a showstopper.