--persist (keep the container alive for inspection) and --debug (enable internal engine logging).
Using --persist to Inspect Containers
By default, containers are cleaned up after execution. Use --persist to keep the container running so you can inspect its state:
Using --debug to See Engine Internals
--debug prints internal engine logs that are normally silent:
[DEBUG] prefixed messages about:
- Container pool operations (acquiring/releasing warm containers)
- Container lifecycle (create, start, stop, remove)
- Persist/cleanup decisions
- Image resolution
Combining Both Flags
Use both--persist and --debug for maximum visibility:
Library Usage
Common Issues and Solutions
Timeout Errors
--persist to see how far the code got:
Out of Memory
No Space Left on Device
/sandbox or /tmp tmpfs is full. Increase the size:
Package Installation Failures
/sandbox which has exec, but the sandbox may be too small:
Runtime Mismatch in Persistent Mode
Debugging Network Issues
Forfiltered mode connectivity problems, use --debug to see proxy logs and test with curl:
Cleanup After Debugging
After using--persist, clean up leftover containers: