All instances now show "Startup failure: Docker returned error code 125"

OS Name/Version: Linux Mint 5.15.0-92-generic

Product Name/Version: v2.4.8 built 29/01/2024

Problem Description:

All instances on one server has now started to produce an error:

Starting Instance - Starting Valheim (Valheim01)… - State: 3.

Startup failure: Docker returned error code 125

If I create a new instance then it works fine. Looking at the servers console output it shows and error:

docker: Error response from daemon: Conflict. The container name “/AMP_Valheim01” is already in use by container “1de6510f2985b724c82395722943d1a3acf2a336ec67ff17acd7159d0785d557”. You have to remove (or rename) that container to be able to reuse that name.

Actions taken to resolve so far:

I’ve tried doing a docker pull cubcoders/ampbase -a as I spotted some others having the same issue but still having the same problem. Also restarted the server and amp to see if that would help but still stuck.

If a restart doesn’t clear them out, you can run docker rm containerID replacing the containerID with what you have above for each that AMP can’t start.

The error I get when trying that is:

Error response from daemon: container 8faa3c26e912ae643582c9211248cd20a72f434ce193fa8aa591a5dbc2e75c37: driver “zfs” failed to remove root filesystem: exit status 1: “/usr/sbin/zfs destroy -r rpool/var/lib/docker/affd8f5b55990f5b19d3aea76e8e132ed93cda9b041d7920276891a8b0eb8986” => cannot open ‘rpool/var/lib/docker/affd8f5b55990f5b19d3aea76e8e132ed93cda9b041d7920276891a8b0eb8986’: dataset does not exist

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