Closed pabloeisenhut closed 5 months ago
Hello, please check https://github.com/truenas/charts/issues/1997
Hey, I'm not sure if I've understood everything correctly... But I tried the following and it didn't work: Fresh installation even without Host Path volumes. GID 1000 did not work either and is somehow not a nice solution. I use fast SSDs so the problem can't be narrowed down to HDD.
But I have also come across a new error: Startup probe failed: Get "http://ip:port/": dial tcp ip:port: connect: connection refused
In this case, I'd need more information. eg logs from the container. The probes failing are a side effect, but we'd need the logs to see why those are failing.
Thanks
I also get the:
Paperless-ngx docker container starting...
Mapping UID and GID for paperless:paperless to 568:568
But this makes no sense if I only use ixVolumes.
After a while it worked, but with Host Path volumes it still doesn't work. Do I understand correctly that you can only use paperless-ngx with your own host path if you have created a user/group with the GID 1000 and applied it to the directories?
After a while it worked, but with Host Path volumes it still doesn't work. Do I understand correctly that you can only use paperless-ngx with your own host path if you have created a user/group with the GID 1000 and applied it to the directories?
You can use other UID/GID, but if you do paperless will re-map those id's and it will take significant time to start. Paperless container do this on every startup.
It does not make a different if you are using hostpath or ixVolumes. as the re-mapping is being done even on non-persistent files.
Fresh installation with Host Path Volumes
Back-off restarting failed container paperless-ngx in pod paperless-ngx