Hi, I actually tried to create a paperless docker instance following your (very detailed and well done) guide on Readthedocs.
Unfortunately, I'm running into an issue at the very end of the script when the paperless service should be executed with sudo:
sudo: /etc/sudo.conf is group writable sudo: /etc/sudo.conf is group writable sudo: unable to open /etc/sudoers: Permission denied sudo: no valid sudoers sources found, quitting sudo: unable to initialize policy plugin
I already tried to modify the file permissions via the Dockerfile with inserting a chmod 640 /etc/sudo.conf line and got rid of the first two issues but was never able to manage the Permission denied on the sudoers file.
I even tried to create the docker instance with a "less-as-possible" modified docker-compose.yml and only changed the local port to 8001 as 8000 is already in use by another service, but had no success.
Does anyone have any idea where to dive deeper into that issue and maybe how fix the root cause? Modifying file permissions seems a bit 'hacky' to me :-)
Hi, I actually tried to create a paperless docker instance following your (very detailed and well done) guide on Readthedocs. Unfortunately, I'm running into an issue at the very end of the script when the paperless service should be executed with sudo:
sudo: /etc/sudo.conf is group writable sudo: /etc/sudo.conf is group writable sudo: unable to open /etc/sudoers: Permission denied sudo: no valid sudoers sources found, quitting sudo: unable to initialize policy plugin
I already tried to modify the file permissions via the Dockerfile with inserting achmod 640 /etc/sudo.conf
line and got rid of the first two issues but was never able to manage thePermission denied
on the sudoers file. I even tried to create the docker instance with a "less-as-possible" modifieddocker-compose.yml
and only changed the local port to 8001 as 8000 is already in use by another service, but had no success. Does anyone have any idea where to dive deeper into that issue and maybe how fix the root cause? Modifying file permissions seems a bit 'hacky' to me :-)