Updating paperless-ngx with docker-compose

[olegkron]

Hi everyone!

Is there a reliable way to update your paperless-ngx running on docker with docker-compose ?

After updating with docker-compose I have lost both my configuration (correspondents, tags, etc) and my data (0 documents in the GUI, luckily still available in the old docker volume directory).
Ideally I'd like to upgrade while keeping the data and the configuration intact.

Please let me know if there is a better way to upgrade your paperless-ngx without going through such a headache.

Many thanks!

Commands run:

docker-compose down
docker-compose pull
docker-compose up

docker-compose file:

version: "3.4"
services:
  broker:
    image: redis:6.0
    restart: unless-stopped
    volumes:
      - redisdata:/data

  webserver:
    image: ghcr.io/paperless-ngx/paperless-ngx:latest
    restart: unless-stopped
    depends_on:
      - broker
      - gotenberg
      - tika
    ports:
      - 8000:8000
    healthcheck:
      test: ["CMD", "curl", "-fs", "-S", "--max-time", "2", "http://localhost:8000"]
      interval: 30s
      timeout: 10s
      retries: 5
    volumes:
      - data:/srv/dev-disk-by-uuid-abcd/paperless/data
      - media:/srv/dev-disk-by-uuid-abcd/paperless/media
      - ./export:/usr/src/paperless/export
      - ./consume:/usr/src/paperless/consume
    env_file: docker-compose.env
    environment:
      PAPERLESS_REDIS: redis://broker:6379
      PAPERLESS_TIKA_ENABLED: 1
      PAPERLESS_TIKA_GOTENBERG_ENDPOINT: http://gotenberg:3000
      PAPERLESS_TIKA_ENDPOINT: http://tika:9998
      PAPERLESS_ADMIN_USER: ***
      PAPERLESS_ADMIN_PASSWORD: ***

  gotenberg:
    image: gotenberg/gotenberg:7.4
    restart: unless-stopped
    command:
      - "gotenberg"
      - "--chromium-disable-routes=true"

  tika:
    image: ghcr.io/paperless-ngx/tika:latest
    restart: unless-stopped

volumes:
  data:
  media:
  redisdata:

[hendrik1120]

The commands you executed are perfectly fine, just map your directories right next time:

    volumes:
      - data:/srv/dev-disk-by-uuid-abcd/paperless/data
      - media:/srv/dev-disk-by-uuid-abcd/paperless/media

It's host:container not the other way around. /srv/dev-disk-by-uuid-abcd/ doesn't exist in the container, so you just saved everything inside the container.

[olegkron]

Thanks! However, I have a full and correct path to my volume there.
I truncated the full dev-disk-by-uuid to abcd for readability.

[hendrik1120]

Please see the /docker/compose directory on compose examples.

[shamoon]

What he's (accurately) saying is your volumes: under webserver is incorrect. I think youre sort of mixing volumes vs bind-mounts.

If you want to use bind-mounts (I do, easier in some ways, but there are pros / cons) it should be SOURCE:TARGET e.g. it should be
/srv/dev-disk-by-uuid-abcd:/usr/src/paperless/data to map that paperless dir to your host dir.

If you want to use volumes, it would be VOLUME:TARGET, e.g.
data:/usr/src/paperless/data (as is in the compose files).

Note the TARGET is the same in both, the target dir inside the paperless container, currently youre mapping to non-existent dir (/srv/dev-disk-by-uuid-abcd doesnt exist) and data is getting lost cause its not saved externally to the container

See https://maximorlov.com/docker-compose-syntax-volume-or-bind-mount/

[hendrik1120]

Yes, exactly @shamoon did a way better job explaining.

Just also be aware that whatever you did in this paperless instance still isn't being saved and will be gone after you change the volume configuration.

[olegkron]

Many thanks @hendrik1120 @shamoon for the clarification!

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.