You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am exploring running the ghcr.io/filecoin-saturn/l1-node:main container in another container runtime environment (k8s) than on Docker via your run.sh and noticed the following error:
2022/11/19 23:42:19 [emerg] 29#29: chown("/usr/src/app/shared/nginx_cache", 101) failed (1: Operation not permitted)
nginx: [emerg] chown("/usr/src/app/shared/nginx_cache", 101) failed (1: Operation not permitted)
I suspect that this is because on (my) k8s the file permission on the /usr/src/app/shared/volume is slightly different than on Docker?
I'm not sure you if this is a real problem or can just be ignored.
The text was updated successfully, but these errors were encountered:
I'm not sure you if this is a real problem or can just be ignored.
This log message is a "real" critical (note emerg = Nginx "Emergency") problem which blocks orderly start-up.
#120 raised to make this easier to understand for future users.
I suspect that this is because on (my) k8s the file permission (...)
It's actually not really that, the reason was just that I tried to run it with more limited Linux capabilities than root, for a better security posture. This would be similar e.g. to "rootless" Docker (or Podman), where I suspect one woul also run int this error (not yet tested).
vorburger
changed the title
nginx: [emerg] chown("/usr/src/app/shared/nginx_cache", 101) failed (1: Operation not permitted)
Support running the container rootless
Nov 23, 2022
I am exploring running the
ghcr.io/filecoin-saturn/l1-node:main
container in another container runtime environment (k8s) than on Docker via yourrun.sh
and noticed the following error:I suspect that this is because on (my) k8s the file permission on the
/usr/src/app/shared/
volume is slightly different than on Docker?I'm not sure you if this is a real problem or can just be ignored.
The text was updated successfully, but these errors were encountered: