Hi, the proxy is internal to the Docker container, it captures HTTPS network traffic and that’s how the archive is created. It sounds like it was a permissions issue with writing to the crawls directory…
Is there anything you needed to do to make it work? Can definitely add it to the docs
To make it work I added a :Z suffix to the -v (volume) option. I think this is specific to Red Hat’s podman and only applicable where SELinux is in use.
What might help more generally is making sure the proxy can never fail to start without throwing an error. Possibly this has already been done; 0.2.1-beta.0 seems to emit more useful errors than 0.1.2.