Has anyone experienced issues with running Jekyll, when spawned as a subprocess inside a docker container. The peculiar thing is that there are no issues when running locally, but when doing the exact same thing inside docker, Jekyll simply hangs at a certain point.
It is spawned from the Java process that is set as the entrypoint of the container. I get no errors from Jekyll, it simply hangs. When attaching to the container I can see both processes are running (Java and Jekyll). It is spawned from within the Java process using the Apache executor framework (org.apache.commons.exec.DefaultExecutor). The following is used for execution:
org.apache.commons.exec.CommandLine.parse(jekyllCommand+" build --destination \""+outputDir+"\""), where jekyllCommand is simply jekyll
The java process does pre-processing and post-processing for Jekyll, and launches it through the command line. Jens (who reported this), and I can both run exactly the same inputs and outputs outside Docker, and it runs fine. There’s no errors from Jekyll outside docker. Jens - what version of Jekyll are you using?