The world isn't saved when docker stops

[koksario]

Hello!
First of all thank you for the opportunity to run my own server

I have a problem with saving my world when I stop container. I use docker compose
I would like to save my world via any command cause I'm gonna restart a whole server each X hours
I brought files of the world from my local PC to the server

root@valheim:~# docker stop coi-valheim-1
coi-valheim-1
root@valheim:~# docker logs coi-valheim-1 | tail -4
ln: failed to create symbolic link '/home/steam/.steam/root': No such file or directory
ln: failed to create symbolic link '/home/steam/.steam/steam': No such file or directory
[Valheim][steam]: Halting server! Received interrupt!
[ODIN][INFO]  - Stopping server /home/steam/valheim
[ODIN][INFO]  - Scanning for Valheim process
[ODIN][INFO]  - Process NOT found!
root@valheim:~# ls -lt /config/worlds_local/ | head -7
total 50744
-rw-r----- 1 ubuntu netdev   46 Sep  6 15:34 PENA1.fwl
-rw-r----- 1 ubuntu netdev 7.9M Sep  6 15:34 PENA1.db
-rw-r----- 1 ubuntu netdev 7.9M Sep  6 15:34 PENA1_backup_auto-20230906153428.db
-rw-r----- 1 ubuntu netdev   46 Sep  6 15:34 PENA1_backup_auto-20230906153428.fwl
-rw-r----- 1 ubuntu netdev   46 Sep  6 14:17 PENA1.fwl.old
-rw-r----- 1 ubuntu netdev 7.9M Sep  6 14:17 PENA1.db.old
root@valheim:~# date
Wed 06 Sep 2023 04:03:02 PM UTC
root@valheim:~#

My docker compose yaml:

version: "3"
services:
  valheim:
    image: ghcr.io/mbround18/valheim
    stop_signal: SIGINT
    ports:
      - 2456:2456/udp
      - 2457:2457/udp
      - 2458:2458/udp
    environment:
      PORT: 2456
      NAME: "..."
      WORLD: "PENA1"
      PASSWORD: "..."
      PUBLIC: 1
      ENABLE_CROSSPLAY: 1
    volumes:
      - /config:/home/steam/.config/unity3d/IronGate/Valheim
      - /opt/valheim/:/home/steam/valheim
      - /backup/:/home/steam/backups

Additional info:

root@valheim:~# docker exec -it coi-valheim-1 bash
root@8b72462293bb:~# odin status
[ODIN][INFO]  - Name: AAAAAA
[ODIN][INFO]  - Players: 0/64#That's not true cause at least I'm online
[ODIN][INFO]  - Map: AAAAAA
[ODIN][INFO]  - BepInEx Enabled: false
root@8b72462293bb:~#

[mbround18]

@koksario

Could you pin this to a specific version in your compose? Change image: ghcr.io/mbround18/valheim to image: ghcr.io/mbround18/valheim:v2.1.3

[exalented]

30 minutes of building lost due to this issue.
Odin is not properly documented. Is there a way to manually save the world? That should be triggered before the container shuts down.

[mbround18]

@exalented I understand how frustrating this can be. Could you please provide more details on how Odin is not properly documented and where you feel the documentation is lacking? According to the hosting guide provided by the Valheim developers, the container should trigger SIGINT. I've extensively tested the shutdown capabilities and saving features on recent releases. However, I cannot account for any mods you might have installed or if you're using an outdated Docker image.

Could you let me know which version of the Docker image you're using and what mods you have installed? This information will help us troubleshoot the issue more effectively.

Thank you for your patience and understanding.

[ericjgoebel]

@exalented There are a couple ways to work around this right now.

1. Go in-game as an admin (requires your ID being on the admin.txt list) and hit pause/ESC and click on save. This does trigger a save but requires logging into the game.
2. Use odin stop like this docker exec tacticalsrealm-valheim-1 odin stop just replace the tacticalsrealm-valheim-1 part with the name of your instance. This will stop the server, but I found that this triggers the save before shutting down. After that wait a minute for the save to complete and then you can use docker compose down (ref ticket I mentioned this here Having to call odin stop because docker compose down doesnt save #812)
3. You could of course increase the frequency of backups and rely on restoring those in such a case because the backup feature is working fine. This is probably an annoying workaround though.

@mbround18 I don't think the recent fix in #813 fixed the issue. I mentioned this as a follow up #812 (comment) but I guess that got missed somehow. I figured it must just be my config and have been working around it since it's only a minor annoyance, but it looks like other people are still experiencing it too.

I have not re-tested this explicitly in the latest few versions but I'm running v3.0.0 with vanilla Valheim right now. I could certainly assist in further testing and info gathering if needed. Thanks for continuing to support this project.