Container stopping and onlly starting when I connect through ssh #789
-
Hello, Since a few days I have a bad behavior of my container, it is just stopping while nobody is connected and no one is able to connect to it anymore. And when I'm connecting on my host through ssh, the docker container is starting by himself... I put CONTAINER ID IMAGE COMMAND CREATED STATUS
a85cab6756c5 mbround18/valheim:latest "/bin/bash /entrypoi…" 35 hours ago Up 8 minutes (healthy) docker compose file : version: "3"
services:
valheim:
image: mbround18/valheim:latest
ports:
- 2456:2456/udp
- 2457:2457/udp
- 2458:2458/udp
environment:
- TYPE=BepInExFull
- "MODS=
https://gcdn.thunderstore.io/live/repository/packages/Grantapher-ValheimPlus_Grantapher_Temporary-9.12.0.zip
"
- PORT=2456
- NAME="*******"
- WORLD="*******"
- PASSWORD="*******"
- TZ=Europe/Paris
- PUBLIC=1
- AUTO_UPDATE=0
volumes:
- ./valheim/saves:/home/steam/.config/unity3d/IronGate/Valheim
- ./valheim/server:/home/steam/valheim
restart: always got this in logs today from the end of the start to the complete stop :
I'm runing docker-ce 25.0.1 on Centos Stream 9 (kernel 5.14.0-412.el9.x86_64) |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
That is super weird, could you try with |
Beta Was this translation helpful? Give feedback.
-
How are you running it? via Also - docker/cli#3914 - possible host issue. |
Beta Was this translation helpful? Give feedback.
-
Thank you for all your suggestions, after a bit of search, I think I just forgot run an loginctl enable-linger $UID |
Beta Was this translation helpful? Give feedback.
Thank you for all your suggestions, after a bit of search, I think I just forgot run an
enable-linger
on my host... Maybe it would be cool to specify it in installation instructions with docker.loginctl enable-linger $UID