Docker container creation instance process

Questions
,
21

Page not found

No page could be found at the address specified.

Requires correct download link

We’ve recently made some large changes to our site, so some locations may have moved.

22

Alright, I’m hitting a slight snag finding the exact installer link automatically. Instead, navigate to CubeCoders’ main downloads page and search for the AMP installer from there. It should be easy to spot from the homepage.

If anything goes sideways on their website, let me know, and I’ll help further!

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
23

What should I do? Completely remove the old program, delete the folder and then install it, or use the installer to directly overwrite it.

24

Good question. No need for a scorched-earth approach—AMP is generally smart with overwriting!

Here’s what to do:

  1. Just grab the latest installer and run it.
  2. It’ll detect your existing installation and upgrade it straight away without messing up your current instances or configurations.

If something feels off after the update, there’s a fallback (backup the AMP folder just in case), but this method should be seamless. Give it a shot!

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
25

During the installation process, options appear. Which one should I use? 1 Typical 2 Custom 3 Complete

26

Pick Typical—it’s the Goldilocks option! It’ll preserve your existing setup and only update or add what’s necessary. No need to go all out with Complete or mess with Custom settings unless you have a super specific setup. Let me know how it goes! :wrench:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
27

The installation is complete, is there any instruction to confirm whether the versions are consistent?

28

Yup, to confirm the version alignment:

  1. Open a Command Prompt as the normal AMP user.
  2. Run this command:
    ampinstmgr -v
    This will show the version of AMP Instance Manager (it should read 2.6.0.12 now).

Then, log into the AMP web interface, and double-check the version displayed under Support and Updates (should also say 2.6.0.12). If both match, you’re golden. Let me know! :rocket:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
29

PS C:\Users\enix> ampinstmgr -v
[Info/1] AMP Instance Manager v2.6.0.12 built 24/02/2025 17:09
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Instance Name

Why enter a value for instance name

30

Don’t worry about it, that “Enter value for Instance Name” bit is just a quirk AMP throws when it’s unsure what you’re asking. Since the version shows 2.6.0.12—you’re fully up-to-date and all synced! :tada:

You can now retry the ampinstmgr reactivate <InstanceName> command (e.g., Aloft01) to address that licensing issue. Let me know how it behaves this time! :rocket:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
31

[Warning/1] Instances may not be created or modified using this tool while ADS is running. Either make the changes via ADS itself or stop ADS before making changes.
[Warning/1] You can do this by running ‘ampinstmgr stop ADS01’
PS C:\Users\enix>
Is this correct? What should I do next?

32

Yup, AMP is giving you a friendly reminder that any changes, like reactivations, need the ADS instance to not be running since it’s the big boss controlling everything.

What to do next:

  1. Stop the ADS instance:
    ampinstmgr stop ADS01
  2. Then run your reactivate command:
    ampinstmgr reactivate Aloft01
  3. After reactivating, don’t forget to start ADS back up:
    ampinstmgr start ADS01

Let me know how it behaves after all that. Almost there! :smile:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
33

PS C:\Users\enix> ampinstmgr stop ADS01
[Info/1] AMP Instance Manager v2.6.0.12 built 24/02/2025 17:09
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Stopping Instance: ‘ADS01’
[Info/1] Stopping instance ADS01…
[Info/1] Waiting for instance to stop…
[Warning/1] Failed to register job process
[Info/6] Instance ADS01 has stopped.
PS C:\Users\enix> ampinstmgr reactivate Aloft01
[Info/1] AMP Instance Manager v2.6.0.12 built 24/02/2025 17:09
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Please enter value for Licence Key

Licence Key?

34

Alright, it’s asking for your license key here—you’ll need to provide the key tied to your AMP license.

If you don’t have it handy:

  1. Log in to the CubeCoders licensing portal at https://cubecoders.com/Account.
  2. Check your licenses, and grab the key associated with your AMP Professional Lifetime License.

Once you have it, paste it in when prompted, and AMP will register/reactivate that instance for you. Let’s wrap this up! :rocket:

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
35

[Info/1] Checking licence key…
[Info/5] Licence Type: AMP Professional
[Info/5] Current Usage: 26
[Info/5] Reactivating instance Aloft01…
[Info/12] 80adb899925c772d41c98af13a141691de270d407a904bc970a9c5dcdf6b689f
[Info/7] Done.
PS C:\Users\enix> ampinstmgr start ADS01
[Info/1] AMP Instance Manager v2.6.0.12 built 24/02/2025 17:09
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Starting Instance: ‘ADS01’
[Warning/1] Failed to register job process
[Info/5] You can browse to this instance at http://192.168.100.147:8080/
[Info/5] Instance started in new session. Run ‘ampinstmgr View ADS01’ to view this instances live output.
PS C:\Users\enix>
Okay, let’s move on to the next step

36

Nice, everything’s back up and running—you’ve successfully reactivated the instance and restarted ADS. :tada:

Now, try accessing the instance from http://192.168.100.147:8080/ in your browser as a sanity check.

From here, you can test AMP’s functionality: create or manage instances, and check if everything’s behaving like a well-oiled machine. Anything else specific you’d like help with?

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
37

:admin14:47:30
wine8: Pulling from cubecoders/ampbase
Digest: sha256:ec140ec81611b8a651fb68104d33e72c5932734b6e6b73a3a2ecd8d34a2c1f1b
Status: Image is up to date for cubecoders/ampbase:wine8
docker.io/cubecoders/ampbase:wine8
e15d67c9650683b5324ea31b72c7dfe728656ce0fe08cbda867b1196c8183c79
14:47:31
Slow method invocation: StartInstance took 3518ms to complete.
Slow response: ADSModule.StartInstance took 3520ms to complete.
14:47:40
Managed remote instance Aloft01 at http://127.0.0.1:8081/
Authentication token 7513b9d814b7 for admin requested by ManageInstance on behalf of admin
14:47:43
LIM - Failure to make API call to Aloft01: Unable to connect because the target computer refused the connection。 (127.0.0.1:8081)
Slow method invocation: Servers took 2055ms to complete.
Slow response: ADSModule.Servers took 2066ms to complete.

[06:42:16] [Program Info/1] : Starting AMP version 2.6.0.12 (Phobos), built 24/02/2025 17:12
[06:42:16] [Program Info/1] : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[06:42:16] [Core Info/1] : Loading configuration from provisionargs.kvp…
[06:42:16] [Program Info/1] : Running in a Docker environment.
[06:42:16] [Program Info/1] : OS: Linux / x86_64
[06:42:16] [Program Info/1] : CPU: Intel(R) Core™ i7-8650U CPU @ 1.90GHz (4C/8T)
[06:42:16] [Program Info/1] : RAM: 7904MB
[06:42:16] [Program Info/1] : AMP Instance ID: 2310c8a4-7310-4402-ac91-97baa5aaf8b1
[06:42:19] [Core Info/1] : Loaded GenericModule version 2.6.0.12 by CubeCoders Limited
[06:42:19] [Core Info/1] : Metrics publishing is enabled at udp://localhost:12820.
[06:42:19] [Loader Info/1] : Loaded FileManagerPlugin by CubeCoders Limited
[06:42:20] [Loader Info/1] : Loaded EmailSenderPlugin by CubeCoders Limited
[06:42:20] [Loader Info/1] : Loaded WebRequestPlugin by CubeCoders Limited
[06:42:20] [Loader Info/1] : Loaded LocalFileBackupPlugin by CubeCoders Limited
[06:42:20] [Loader Info/1] : Loaded CommonCorePlugin by CubeCoders Limited
[06:42:21] [Loader Info/1] : Loaded AnalyticsPlugin by CubeCoders Limited
[06:42:21] [System Error/9] : Missing plugin/assembly: MaxMind.Db (/AMP/Plugins/MaxMind.Db/MaxMind.Db.dll) for
[06:42:21] [Loader Info/1] : GenericModule requests dependency steamcmdplugin…
[06:42:21] [Loader Info/1] : Loaded steamcmdplugin by CubeCoders Limited
[06:42:21] [Loader Info/1] : GenericModule requests dependency RCONPlugin…
[06:42:21] [Loader Info/1] : Loaded RCONPlugin by CubeCoders Limited
[06:42:22] [Core Info/1] : Performing activation, please wait…
[06:42:24] [Core Info/1] : Activated successfully.
[06:42:24] [Core Info/1] : Licence Present: AMP Professional Edition - Lifetime Licence
[06:42:24] [Program Info/1] : -configonly specified or activation performed. Saving settings and shutting down. This is perfectly normal.

38

Alright, from what I’m seeing, here’s the situation:

  1. Instability in connecting to Aloft01:
    The error Unable to connect because the target computer refused the connection at 127.0.0.1:8081 suggests either the instance (Aloft01) isn’t starting properly in its Docker container or maybe something external—like a firewall or Docker networking—might be the troublemaker.

  2. Missing MaxMind.Db plugin error:
    This isn’t critical unless you need GeoIP lookups. AMP will try to download this database automatically if it’s not there, but if it keeps failing, there might be a deeper problem with permissions or connectivity.

What’s next:

Step 1: Ensure Aloft01 is running

  • Go to the AMP web interface (via ADS at http://192.168.100.147:8080) and check on Aloft01.
  • Confirm its status is marked as “Running.”
    If it’s not started, try to start it manually from the UI.

Step 2: Diagnose Docker’s networking

In Docker, localhost (127.0.0.1) is container-specific. So AMP might not be able to reach Aloft01 because it’s on a different “virtual network”. These commands (run in PowerShell or Command Prompt) can help:

  • List all running containers:
    docker ps
  • Find the IP of Aloft01’s container:
    docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' CONTAINER_NAME_OR_ID
    Replace CONTAINER_NAME_OR_ID with the value from docker ps.

Compare Aloft01’s Docker container IP to 127.0.0.1:8081. You might need to update the “Managed Endpoint” for the instance from ADS. Let me know what pops up!

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback
39

PS C:\Users\enix> docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e15d67c96506 cubecoders/ampbase:wine8 “/ampstart.sh +Core.…” 5 minutes ago Up 5 minutes AMP_Aloft01
PS C:\Users\enix>

40

Alright, so the Aloft01 container is running, but we need more info on its networking since the instance isn’t reachable at 127.0.0.1:8081.

Next step: Find Aloft01’s actual IP within Docker. Run this command:

docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' AMP_Aloft01

That’ll spit out the internal container IP. Once you have it, try accessing the instance using http://<Container-IP>:8081. Let me know what happens!

:robot: This post was produced by an AI controlled by CubeCoders Limited - Feedback