Setting Up Paperless-NG with Portainer

  • Hello,


    unfortunately I am not very into using Dockers and this is the reason I need some support installing Paperless-NG with Portier.

    I tried to install it with the following modified compose file: paperless-ng/docker/compose/docker-compose.portainer.yml

    My file for the stack had the following input:

    Unfortunately after the stack is deployed it shows me that the container is running but unhealthy in Portainer. I can't get access to the console, too.

    Is there anything I have to change?


    Would be great to get some support over here and get this Docker to work in OMV. Maybe there is even an easier was as with Portainer.


    Thanks,

    Chris

  • If you use this file as stack in portainer, you have to change the local volume definition or the files will end up inside the portainer_data volume somewhere:


    Code
      volumes:
          - ./export:/usr/src/paperless/export     # change here
          - ./consume:/usr/src/paperless/consume   # change here


    and the other definitions use named docker volumes. Make up your mind, if you want that.

    What you need to put for the volumes depends how you set up docker on omv and where you want your data to live.


    Which one of the containers is not working? In the stack there are three: broker, db and webserver and why can't you look into the logs?

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • For testing purposes, can you try this instead:

    Papermerge seems to do the same and it's more actively maintained:

    ciur/papermerge: Open Source Document Management System for Digital Archives (Scanned Documents) (github.com)


    Login via ssh

    mkdir papermerge

    cd papermerge

    nano docker-compose.yml


    Copy/Paste the below code editing both instances of :

    Code
          - POSTGRES_USER=dbuser # Edit this to your liking
          - POSTGRES_PASSWORD=dbpass # Ditto
          - POSTGRES_DB=dbname #Double Ditto

    The 2 instances need to match each other:


    Save it and run:

    docker-compose up -d


    Access the webfront via http://LAN IP of HOST:38000 Changed to 38000 due to portainer already runs on port 8000

    See if it works as expected.

  • I changed the stack to the following:

    Zitat

    Does this one look correct?

    The container "webserver" is shown as unhealthy in Portainer.

    There is also no IP adress & publish ports for this container available?


    Don't know what else I can do?!


    Soma: Thanks for your help. Already thought about using Papermerge but it seems Paperless has some advantages compared to Merge.

  • Your volumes are still wrong:

    If you want to use this drive,

    Code
    /srv/dev-disk-by-label-Backupintern/


    Login with user who has ID 1000 (as you marked it on the YML)


    mkdir /srv/dev-disk-by-label-Backupintern/paperless_vol



    This is how your YML/stack should be:

  • Thanks!

    I now changed it to the following:

    But I still have the issue that the container isn't working.

    Any further ideas?

  • "Isn't working" is not much of a description of your problem.


    • Which containers are runningß
    • How do you see there is a problem?
    • Post the logs


    Or buy me a new cystal ball.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Ok, just did this on a fresh OMV6 install and it runs on 1st attempt:


    YML/stack pasted into Portainer STACK creator:



    Went to the Container paperless_webserver_1 and created the super user as instructed on the original docker-compose.yml via Exec Console (Symbol >_ on Portainer)


    Accessed the web-front with:

    http://LAN_IP:8010

    user=papertest and the password created.


    presto:

  • "Isn't working" is not much of a description of your problem.


    • Which containers are runningß
    • How do you see there is a problem?
    • Post the logs


    Or buy me a new cystal ball.

    So after the stack is deployed I have the following 3 containers:

    -paperless_webserver_1

    -paperless_db_1

    -paperless_broker_1


    After trying to run the console in the webserver I receive the error message:

    "Failure

    Container 92d3589638dddc10aa91b3de549abcf6359bbe4c0fa0db3efa04f9bd109abfe6 is restarting, wait until the container is running"

    Also the container is shown as not healthy and there is no ip or ports shown.


    Logs are shown the following:

    Maybe I have to switch to OMV 6 with a fresh install ;(

  • Maybe I have to switch to OMV 6 with a fresh install

    Docker containers aren't bound to the Debian version, the YML should have the necessary apps to run in.


    Let me try to set it on a OMV5 VM I have here to see what happens.

  • ChrisBuzz

    Hat das Label gelöst hinzugefügt.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!