Following up on @ajphillips initial issue, I had a comparable issue when building my own docker container from the published base container and was able to resolve the issue by removing the --no-sandbox argument for chrome-pdf. In my case, I had copied that over from my local install, and did not actually require the argument when building from the base image. Hope this helps anyone else that may be in the same situation.