Startup Issue with Application Deployment - Notification errors regarding docker instance conflicts

System Information

Field Value
Operating System Linux - Ubuntu 22.04.3 on x86_64
Product AMP ‘Decadeus’ v2.4.6.8 (Mainline)
Virtualization HyperV
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Problem Description

  1. Startup Errors as listed below with docker
  2. Catastrophic crashing of App Instances at around 45 Instances.

Ubuntu show 40% free space on the drive, 150GB/200GB of ram in use.
AMD EPYC 7262 Server Processor, Intel DC SSD, 200GB Registered ECC Ram

Issue

AMP is up to date.
17:26:00
Start for instance Ark2-Aberration was requested, but it is already running.
17:26:05
Start for instance Ark6-LostIsland was requested, but it is already running.
17:26:10
Start for instance Ark20-DK was requested, but it is already running.
17:26:15
docker: Error response from daemon: Conflict. The container name “/AMP_Starbound01” is already in use by container “27ea6c6b6a684da027de92331bb8a1ae90701116cd65aafe88b90beaaaf932d0”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:20
docker: Error response from daemon: Conflict. The container name “/AMP_ValheimMistlands01” is already in use by container “87f11997a12931540d1b6b997f255e4a2387b827095f9f015b8b54f965116638”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:26
docker: Error response from daemon: Conflict. The container name “/AMP_Terraria01” is already in use by container “8338c493b848413bad3f3ff6c648df0408f4114074dfc51d6c9cc61e378babdd”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:31
docker: Error response from daemon: Conflict. The container name “/AMP_DSTCaves01” is already in use by container “eba6f9fc71ba5670e12df7f00ffc6bdef3246f0a289f3ac4bc3190da2bdc0d6e”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:36
docker: Error response from daemon: Conflict. The container name “/AMP_Icarus01” is already in use by container “3274c26738b9a6e2bd1befb9a4ec627f4937cc602e3ac2709ddd80b11a9a3297”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:41
docker: Error response from daemon: Conflict. The container name “/AMP_MCJava0701” is already in use by container “45d043801ebf1886acff03465ee5c1461194fc08f8103a2ee5ee2c2b6febf2dc”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:46
docker: Error response from daemon: Conflict. The container name “/AMP_MinecraftJava601” is already in use by container “5476d3177540fc4d363487f55f7f67193fb58033b254d21a85b6452dc9a0431b”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:52
docker: Error response from daemon: Conflict. The container name “/AMP_MinecraftJava501” is already in use by container “9d0c84dbb0cc3da1c20a8c1d3e7a7287dd96d523e316ec2a8c219581e4b3eadf”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:26:58
docker: Error response from daemon: Conflict. The container name “/AMP_MinecraftJava401” is already in use by container “9562c9bf6ae3991af6295ea4179ef30fa91eb5a362d783f4ea058faf16cbc237”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:27:03
Slow method invocation: Login took 2949ms to complete.
Slow response: Core.Login took 2954ms to complete.
docker: Error response from daemon: Conflict. The container name “/AMP_MinecraftJava301” is already in use by container “897caa0f6d7ef91d4ae2be55b31bf318257411824403105c6e397a19b25d90da”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:27:08
docker: Error response from daemon: Conflict. The container name “/AMP_MinecraftJava201” is already in use by container “5cc84e3092e354e66a084b43cc992d13c5dadbcb189cd4acb9c0d9b605e0619d”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:27:13
docker: Error response from daemon: Conflict. The container name “/AMP_MinecraftJava101” is already in use by container “9fba47b348796fe9111f6dfdc6e9f662c300c0c3288e8705e5a529ae91cfe9e9”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:27:19
docker: Error response from daemon: Conflict. The container name “/AMP_FrozenFlame0101” is already in use by container “6430e238442cf8b49fb7d0d158b748f6ce2b4e0602098591f47f16a4f40c6660”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:27:24
docker: Error response from daemon: Conflict. The container name “/AMP_TMLCalamity01” is already in use by container “be672a054915f3dbda99cf3a4a75221b3b0c8812a1dfc55ce3c76c59d7db9932”. You have to remove (or rename) that container to be able to reuse that name.
See ‘docker run --help’.
17:27:34
Start for instance TML1401 was requested, but it is already running.
17:27:39
Start for instance Satisfactory01 was requested, but it is already running.
17:27:44
Start for instance SpaceEngineers01 was requested, but it is already running.
17:27:49
Start for instance Empyrion01 was requested, but it is already running.
17:27:54
Start for instance AmongUs01 was requested, but it is already running.

Reproduction Steps

  • upgraded to latest release
  • reboot the os
  • wait for system to fully boot

Is ampinstmgr itself up to date?

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