No AMP instances are currently set to start automatically on boot

[Tranquill6]

I am running the ubuntu version of docker-amp on my unraid machine, and I configured it to use Java version 17, and I followed the instructions for a MAC address. Upon starting this up, it just repeats the last lines below, namely around no amp instances being set to start automatically on boot. The module, by default, is configured to ADS so, I am unsure why this is happening.

Setting up openjdk-17-jre-headless:amd64 (17.0.11+9-1~22.04.1) ...
update-alternatives: using /usr/lib/jvm/java-17-openjdk-amd64/bin/java to provide /usr/bin/java (java) in auto mode
update-alternatives: using /usr/lib/jvm/java-17-openjdk-amd64/bin/jpackage to provide /usr/bin/jpackage (jpackage) in auto mode
update-alternatives: using /usr/lib/jvm/java-17-openjdk-amd64/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode
update-alternatives: using /usr/lib/jvm/java-17-openjdk-amd64/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode
update-alternatives: using /usr/lib/jvm/java-17-openjdk-amd64/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode
Installed openjdk-17-jre-headless
[custom-init] No custom files found, skipping...
[ig-init] done.
[Info/1] AMP Instance Manager v2.5.0.12 built 30/05/2024 00:03
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] No AMP instances are currently set to start automatically on boot.
[Info/1] AMP Instance Manager v2.5.0.12 built 30/05/2024 00:03
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] No AMP instances are currently set to start automatically on boot.
[Info/1] AMP Instance Manager v2.5.0.12 built 30/05/2024 00:03
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV

[raptordmg]

I'm also having this issue with the Alpine branch as well. Looks like some sort of config issue within AMP.

[lcase711]

Any solution to this as I am experiencing the same thing

[hydazz]

The setup logic has become dodgy for some reason, can be fixed by running s6-setuidgid abc ampinstmgr SetStartBoot Main yes inside the container, then restarting. I'll try fix the logic thats supposed to make it start on boot when i get a min