Problem Description: Attempting to start a V Rising instance, gets stuck at Application State: Preparing to start … absolutely nothing in the console at all. If I click update, console shows downloading of the update and all that, but nothing when I click start. Sits that way forever.
I have not, nor do I have docker setup on this machine. I will try that next, I do see the notice on the modal lol … I may have overlooked this prior. Haha
Followed the instructions, the container refuses to start, cant manage it to view logs because its not running… nothing really in the logs. Starting to wonder if V Rising actually works at all with AMP.
Yeah used the script, appreciate the heads up on that! So it seems to try to start then die. Lemme share what the top level console shows…
Starting the instance:
15:14:05 8700d51383df87b5a2bdd0c5c63d3e92e5c4fbaadec3d5d0977b0cb001ce0d17
15:14:06 Managed remote instance Testing01 at http://127.0.0.1:8083/
Authentication token for root requested by ManageInstance on behalf of root
Give it a good 10 seconds and then the ui shows the instance is not running…
Even tried updating container:
15:06:31 Upgrading instance Testing01
Using cached archive: /home/amp/.ampdata/instances/AMPCache-Mainline-2412.zip
15:06:33 wine: Pulling from cubecoders/ampbase
Digest: sha256:b5158a434a6b8b5af2cfe6f76b5fecbb5cd093948e23805c267f87c879b17d5f
Status: Image is up to date for cubecoders/ampbase:wine docker.io/cubecoders/ampbase:wine
15:06:34 Slow method invocation: UpgradeInstance took 2860ms to complete.
Slow response: ADSModule.UpgradeInstance took 2861ms to complete.
Looking through the AMP log file at the moment, socket error address already in use, but I only have the one container.