I would guess that there is some permissions problem in /srv/jekyll.
I would launch your container with a shell
podman run -p 4000:4000 -v $(pwd):/srv/jekyll:Z jekyll/jekyll:pages /bin/sh And then check the permissions on the directory?
then do a `mkdir /srv/jekyll/foo`
If this fails, most likely is is something to do with User Namespace.
So, it turns out that the upstream container is using su-exec to launch jekyll, which is why the directory creation has the wrong permissions (and fails). There's an obvious fix for me for this one container; however, my experience points out that it would be good to have a more generalized set of instructions for users who are downloading upstream Docker images that use su-exec in their entrypoints. -- -- Josh Berkus Kubernetes Community Red Hat OSPO