Skip to content
This repository has been archived by the owner on Feb 19, 2021. It is now read-only.

Consuming works but where are the documents? #666

Open
ictIntdev opened this issue May 25, 2020 · 7 comments
Open

Consuming works but where are the documents? #666

ictIntdev opened this issue May 25, 2020 · 7 comments

Comments

@ictIntdev
Copy link

I have installed the paperless instance on a docker (container in a QNAP NAS). It looks okay, the docker is running, I managed to create a superuser (paperless) and the documents I created in the consume directory are disappearing so it looks like all working fine. But in the webinterface I don't see the consumed documents.... What could be wrong? Any help is welcome!

@totti4ever
Copy link

Do both containers (consumer and server) share the media and data folder? If they are not set as volume on both they live only in their own container and the server cannot see the metadata and files from the consumer container

@ictIntdev
Copy link
Author

Thanks, according to the docker-compose.yml they do:
both containers have:
volumes:
- data:/share/CACHEDEV1_DATA/Container/container-station-data/application/paperless/data
- media:/share/CACHEDEV1_DATA/Container/container-station-data/application/paperless/media

But maybe there's a "docker-compose" or command or anything else to check if it's really truth?

@totti4ever
Copy link

totti4ever commented May 26, 2020

Well, you should be able to able to see the contents of those folders in your file system.
I'm wondering why your image internal pathes are that different to mine, which image are you using?

mine are (image: pitkley/paperless)

    volumes:
        - ./data:/usr/src/paperless/data
        - ./media:/usr/src/paperless/media

@ictIntdev
Copy link
Author

I'm using a QNAP NAS and that's the directory where all the containers are in.
I added the output of
docker inspect -f '{{ .Mounts }}' containerid
for both containers. Maybe you can see there anything strange.
volumes_consumer.txt
volumes_webserver.txt

@ictIntdev
Copy link
Author

I found the files.... in another directory. But why?
/share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/volumes/39208b929ca164b099bfbf7c5edee060c550f81dc0d6eeebb3f13e5f24fb35a0/_data/documents/originals

@totti4ever
Copy link

Thanks, according to the docker-compose.yml they do:
both containers have:
volumes:

  • data:/share/CACHEDEV1_DATA/Container/container-station-data/application/paperless/data
  • media:/share/CACHEDEV1_DATA/Container/container-station-data/application/paperless/media

But maybe there's a "docker-compose" or command or anything else to check if it's really truth?

I don't really get those lines. From my knowledge it is
path_on_host:path_in_container
So why are those CACHEDEV...folders on the righthandside?

@LorenzBischof
Copy link

LorenzBischof commented May 30, 2020

@totti4ever is correct. The reason that the files are in /share/CACHEDEV1_DATA/Container/container-station-data/lib/docker/volumes/39208b929ca164b099bfbf7c5edee060c550f81dc0d6eeebb3f13e5f24fb35a0/_data/documents/originals is that you are using named volumes and then Docker manages the volumes for you. If you want to specify where the files are located on the NAS, then you need to use a path as the first parameter (before :). It should work with named volumes, but your container path is probably wrong.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants