Stump in docker does not start normally after last update (0.0.5)

[Cantello]

After updating the docker container to 0.0.5, the web app does not start up correctly anymore. Docker log files just say:

2024-08-21T06:51:30.857916397Z Adding user stump with uid 1000
2024-08-21T06:51:30.886926027Z Adding system user 'stump' (UID 1000) ...
2024-08-21T06:51:30.886948374Z Adding new user 'stump' (UID 1000) with group 'stump' ...
2024-08-21T06:51:30.951223245Z Not creating home directory '/home/stump'.
2024-08-21T19:29:11.136315001Z Group gid 1000 already exists
2024-08-21T19:29:11.166849370Z User stump with uid 1000 already exists
2024-08-22T04:02:53.589987182Z Group gid 1000 already exists
2024-08-22T04:02:53.604546861Z User stump with uid 1000 already exists

... and it stays there. I read about the problem with the profile but that was only for new installations and not for the docker container, correct?
Stump runs on a debian computer within docker.

[aaronleopold]

Hm. I personally keep duplicate instances on my own server (latest, nightly, experimental) which is running Ubuntu and I didn't experience an issue upgrading from 0.0.4 to 0.0.5. I'm curious to see what might be happening on your end

I read about the problem with the profile but that was only for new installations and not for the docker container, correct?

Correct

Can you confirm you have your verbosity set? If it isn't, or it is set to 0 (off), could you set it to 3 and share what the container outputs?

[Cantello]

It should be enabled, I set it in docker-compose.yml but the output has not changed... What am I missing here?

  stump:
    image: aaronleopold/stump:experimental
    container_name: stump
    volumes:
      - /opt/stump:/config
      - /mnt/Stuff:/data
    ports:
      - 10801:10801
    environment:
      - STUMP_CONFIG_DIR=/config
      - PUID=1000
      - PGID=1000
      - STUMP_VERBOSITY = 3
    restart: unless-stopped

edit: I removed the experimental tag, pulled the docker image anew, deleted the database and it is now working again. Verbosity is correct as well, lots of messages in the docker logs.

[aaronleopold]

Ahh okay, I assumed you were on a versioned tag.

The experimental and nightly tags are generally less stable, experimental being the least stable and "bleeding edge." It's possible something was merged which caused a break for the experimental image, I'll be sure to check before it eventually makes its way to nightly.

[Cantello]

Thanks for the help, I still had an old installation, and I guess this was from back then. It's working now - except for speed issues, open a new discussion or should I describe the problem here?

[aaronleopold]

It's working now - except for speed issues, open a new discussion or should I describe the problem here?

Open an issue detailing what's going on and we can get it sorted out