Application Deployment - Instance ___ fails to stop

Technical Support
,
1

System Information

Field Value
Operating System Linux - Ubuntu 24.04.1 on x86_64
Product AMP ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization None
Application Application Deployment
Module ADSModule
Running in Container No
Current State Indeterminate

Task

Stop instance

Problem Description

Issue

Attempting to stop any instance doesn’t work, and it won’t restart from configuration changes either. This occurs with both my vintage story and Minecraft instances.

Reproduction Steps

  • Press stop instance
  • Check deployment log
  • Deployment log says instance ___ failed to stop
2

Right click the instance and hit View Logs to see what’s going on inside it

3
4

Weird, it looks fine as far as I can tell. Is your ampinstmgr package up to date?
You can run ampinstmgr version to check

5

[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:58
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV

6

What happens if you run ampinstmgr stop TheInstanceYouWantToStop01 ?

7

[Info/1] AMP Instance Manager v2.6.0.6 built 20/11/2024 20:58
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Stopping Instance: ‘Field01’
[Info/1] Stopping instance Field01…
Error response from daemon: cannot kill container: AMP_Field01: Cannot kill container b2b6a25acfb5c4eaed453a8b8a71bdd40d56625c255924c83044f05d35c06520: unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied
: unknown
[Info/1] Instance Field01 failed to stop.

8

Did you ever add the amp user to the docker group?

9

Through checking this, I realised docker itself was not running. From the error I was getting I found this: docker - Error creating default "bridge" network: cannot create network (docker0): conflicts with network (docker0): networks have same bridge name - Stack Overflow

I have permission now but instances won’t stay open now.

edit: I fixed this and got them in their containers, but I now still have the issue of permission, amp is assigned to the docker group and docker is running.

Stopping instance Field01…
Error response from daemon: cannot kill container: AMP_Field01: Cannot kill container abee2135474913aafcbd52f2146d267ebb1df38bc7bc71ae4421fb1e2bc003dd: unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied
: unknown

edit:edit: I tried using “docker kill (instance)” in non-sudo and permission is denied

final edit: My main issue with something to do with AppArmor. Everything functions after using “sudo aa-remove-unknown”

10

Good find! Great to hear you got things rolling again

11

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