Replies: 1 comment 5 replies
-
Assuming you mount a directory from your mac this is not going to work. AFAIK the mac only allows you access to your uid so you cannot chown that to something different. An easy way to make the user in the container match your user on the host is by using |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When running a jekyll website e.g. https://github.com/agrc/gis.utah.gov, the site will build if there is no content written to the volume from the container. e.g.
.jekyll-cache/
and_site/
. This will be the case on a fresh checkout or when creating a new blog.podman run -ti --rm --volume $PWD:/srv/jekyll --env JEKYLL_ROOTLESS=1 --publish 4000:4000 docker.io/jekyll/jekyll:4 jekyll serve --incremental --livereload
If you stop the container and run it again, every file in those two container generated folders reports the following error:
The permissions look normal to me. Below
_site/
was generated by the container andabout/
was cloned from github.This happens when using a brand new jekyll blog as well.
It would be great if the permissions could be corrected or the files ignored. The website takes a minute to generate so having to delete this content every time i want to start the container is a paper cut. This seems to only affect folks running SELinux.
my machine info
Beta Was this translation helpful? Give feedback.
All reactions