Startup Issue with Valheim - Docker container naming conflict after server reboot

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Decadeus’ v2.4.6.6 (Mainline)
Virtualization Docker
Application Valheim
Module GenericModule
Running in Container Yes
Current State Sleeping

Problem Description


Whenever I perform a reboot on my server, it fails to restart the instances running through Docker. The error I receive is:
Startup failure: Docker returned error code 125
The logs provide the following details:
docker: Error response from daemon: Conflict. The container name “/AMP_Valheim01” is already in use by container “253cb184ef6a196f5e9316888f5e302e386800056b1b390b438832bea062c48a”. You have to remove (or rename) that container to be able to reuse that name.

My Valheim instance is set to start on boot.

Is there a way to auto start my docker instances after a reboot ? Because I need to manually restart the server after each reboot

Reproduction Steps

  • Run a server instance in a docker container
  • Set it to auto start up on boot
  • Reboot AMP Host machine

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.