I have closely followed the docker route on the Installation manual, I did not change any configurations and I successfully configured and started the docker images for paperless. I can open paperless on http://localhost:8000/admin/
I am experiencing difficulties with the consumer though. It seems every time I start or restart both containers, the consumer will actually process the PDFs inside the consume directory of the project, but it will do this only _once_ after I start / restart. If I add files later, they just won't get consumed.
I checked the container's statuses with
➜ paperless git:(master) ✗ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a4cfba2626d8 paperless_consumer "/sbin/docker-entryp…" 43 minutes ago Up 14 minutes paperless_consumer_1
8cccb76c57cf paperless_webserver "/sbin/docker-entryp…" 44 minutes ago Up 14 minutes (healthy) 0.0.0.0:8000->8000/tcp paperless_webserver_1
And they seem to be up and running, but I need to restart the containers for the consumer to do something. I checked the logs at http://localhost:8000/api/logs/, but there is no output except for the files that have been consumed at startup.
Is this a bug or do I need to configure something that is not in the setup docs to make the consumer constantly check the consume directory?
The question is: _Should_ this work when you complete and stick to the docker route on the Installation manual
I could just confirm that my local folder is properly mounted using
$ docker exec paperless_consumer_1 ls /consume
(930644)_28.02.2019.pdf
(930644)_31.07.2018.pdf
it just does not process them.
Then I added more files and ran
$ docker exec paperless_consumer_1 /usr/src/paperless/src/manage.py document_consumer
I can see in my console that the python script processes the files currently in the directory. When I add more files, it does not recognize a change or scan the directory after a timeout.
Ok, so it does work with --no-inotify
$ docker exec paperless_consumer_1 /usr/src/paperless/src/manage.py document_consumer --no-inotify
so it seems that this is the problem. I am using docker on macOS, inotify seems to be recognized as available while it does not really work
Ok, here is how you work around that bug:
Edit docker-compose.yml, change line 52 from
command: ["document_consumer"]
to
command: ["document_consumer", "--no-inotify"]
Run
docker-compose up -d
Hi @LukasBombach! You're actually hitting #520 and the docs on ReadTheDocs are OutOfDateâ„¢.
Here's the latest... and let's see if we can get some traction on that bug.
Thanks man. Btw, in the (new) docs you write that this happens in an NAS env. This happens when you use the docker route.
@LukasBombach we love PR's :)
Ok, give me some time :)
Man I spent the whole day on this same issue, it didn't bother me to check previous issues as I thought the docs were OK.
@lucaskolstad any news on the PR to fix this typos\errors?
@Maxiride, I think you meant @LukasBombach?
@Maxiride i never created a PR since I paused my paperless project for now
thanks @danielquinn
Most helpful comment
Ok, here is how you work around that bug:
Edit
docker-compose.yml, change line 52 fromto
Run