[Bug]: Login data, users etc. are lost after update of the docker container image

[463]

Installation Method

Docker

The Problem

After update of the docker-hub image portainer/portainer-ce:latest the saved options seems to be completely lost. The first login must be done with admin/stirling. All user are not available anymore and I believe that also all other adjustments in the options are lost.

Version of Stirling-PDF

2.1.4

Last Working Version of Stirling-PDF

No response

Page Where the Problem Occurred

No response

Docker Configuration

Relevant Log Output

Additional Information

No response

Browsers Affected

No response

No Duplicate of the Issue

• I have verified that there are no existing issues raised related to my problem.

[dosubot]

Hi @463! I'm Dosu and I’m helping the Stirling-PDF team.

Your login data and user settings are lost after updating the Docker container because the /configs directory, which contains the internal database and all configuration files, is not mounted as a persistent volume. By default, Docker containers are ephemeral—any data not stored in a mounted volume will be wiped when the container is recreated or updated. Stirling-PDF stores all user accounts, settings, and options in /configs (including the database file stirling-pdf-DB-2.3.232.mv.db). If this directory isn’t mapped to a location on your host, everything resets to defaults after an update, and you’ll see the initial login screen with admin/stirling credentials source.

To fix this, update your Docker configuration to mount a host directory to /configs. For example, with Docker Compose:

services:
  stirling-pdf:
    image: stirlingtools/stirling-pdf:latest
    ports:
      - "8080:8080"
    volumes:
      - ./stirling-pdf-configs:/configs
      - ./stirling-pdf-data:/usr/share/tessdata # OCR data (optional)
    environment:
      - DISABLE_ADDITIONAL_FEATURES=false

Or with docker run:

docker run -d \
  --name stirling-pdf \
  -p 8080:8080 \
  -v "$(pwd)/stirling-pdf-configs:/configs" \
  stirlingtools/stirling-pdf:latest

Make sure the host directory (e.g., ./stirling-pdf-configs) is not deleted between updates, and check that the container has permission to read/write to it. This will preserve all users, settings, and options across updates source.

If you want, share your Docker configuration and I can help review it for persistent storage issues. Regularly back up your /configs directory to avoid accidental data loss.

Let me know if you need help with specific config details!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}