Docker container creation instance process

Questions
,
41

PS C:\Users\enix> docker inspect -f ‘{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}’ AMP_Aloft01

Error: No such object: AMP_Aloft01
PS C:\Users\enix>

42

Oof, that’s weird—Docker clearly showed AMP_Aloft01 is running, so it should exist. It’s possible the container name listed under docker ps has a slight variation (or maybe a typo crept into the command).

Let’s re-check the container name exactly as it appears. Run:

docker ps

Take note of the CONTAINER ID or the full NAME of the container listed (like AMP_Aloft01), and run the inspect command again with that exact name or ID:

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

Post back what you’ve got; we’ll untangle this networking madness. :sweat_smile:

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

2025-03-03 15:30:21 useradd: warning: the home directory /home/amp already exists.
2025-03-03 15:30:21 useradd: Not copying any file from skel directory into it.
2025-03-03 15:30:21 [Info] AMPStart for Docker - v23.07.1
2025-03-03 15:30:21 [Info] Performing first-time container setup…
2025-03-03 15:30:21 [Info] Container setup complete.
2025-03-03 15:30:21 [Info] No missing dependencies to install.
2025-03-03 15:30:23 [Info/1] AMP Instance Manager v2.6 built 25/10/2024 12:24
2025-03-03 15:30:23 [Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
2025-03-03 15:30:23 AMP Instance Manager
2025-03-03 15:30:23 Syntax: ampinstmgr [Flags] [Operation] [Arguments] (Optional Arguments)
2025-03-03 15:30:23
2025-03-03 15:30:23 Available Flags:
2025-03-03 15:30:23
2025-03-03 15:30:23 --nocache : When creating/updating instances, do not use an existing cached copy of AMP
2025-03-03 15:30:23 --silent : Suppresses all output
2025-03-03 15:30:23 --advanced : Show advanced operations when using the help command
2025-03-03 15:30:23 --docker : When creating/starting instances, start the instance inside a Docker container (requires root or a user with docker access)
2025-03-03 15:30:23 -version : Display the version and exit
2025-03-03 15:30:23
2025-03-03 15:30:23 Available Operations:
2025-03-03 15:30:23
2025-03-03 15:30:23 --BrowseInstance [Instance Name]
2025-03-03 15:30:23 Browse to an instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --ChangeInstanceStream [Instance Name] [Release Stream] (Force)
2025-03-03 15:30:23 Switch an instance to a different release stream
2025-03-03 15:30:23
2025-03-03 15:30:23 --CreateInstance, -c [Module] [Instance Name] [IP Binding] [Port Number] [Licence Key] [Admin Username] [Admin Password] [Provision Settings]
2025-03-03 15:30:23 Create a new standalone AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --DeleteInstance, -d [Instance Name] (Skip Verification)
2025-03-03 15:30:23 Delete an existing AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --Help, -? (Command)
2025-03-03 15:30:23 Display Help
2025-03-03 15:30:23
2025-03-03 15:30:23 --LastLog [Instance Name]
2025-03-03 15:30:23 View the most recent log file for a given AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --QuickStart, -quick [Username] [Password] (IP Binding) (Port) (Provision Settings)
2025-03-03 15:30:23 Create an ADS instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --RebindInstance [Instance Name] [IP Binding] [Port Number]
2025-03-03 15:30:23 Change the IP/Port binding of an existing AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --ReconfigureInstance [Instance Name] [Provision Settings]
2025-03-03 15:30:23 Reconfigure an AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --RepairAuth, -magic [Mode] [Auth Server URL]
2025-03-03 15:30:23 Repairs the authentication configuration for ADS and all instances
2025-03-03 15:30:23
2025-03-03 15:30:23 --ResetLogin, -e [Instance Name] [Username] [Password]
2025-03-03 15:30:23 Reset a standalone instances login details
2025-03-03 15:30:23
2025-03-03 15:30:23 --RestartAllInstances (Instances) (Delay)
2025-03-03 15:30:23 Restart all AMP instances
2025-03-03 15:30:23
2025-03-03 15:30:23 --RestartInstance, -r [Instance Name]
2025-03-03 15:30:23 Restart a running AMP instance. If the instance is already stopped it will be started.
2025-03-03 15:30:23
2025-03-03 15:30:23 --SetStartBoot, -x [Instance Name] [Start On Boot]
2025-03-03 15:30:23 Set boot-time flag
2025-03-03 15:30:23
2025-03-03 15:30:23 --ShowAllInstancePorts
2025-03-03 15:30:23 Show port usage for all instances
2025-03-03 15:30:23
2025-03-03 15:30:23 --ShowInstanceInfo, -i [Instance Name]
2025-03-03 15:30:23 Show the information for a given instance.
2025-03-03 15:30:23
2025-03-03 15:30:23 --ShowInstancePorts [Instance Name] (Include AMP Port)
2025-03-03 15:30:23 Show port usage by a specific instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --ShowInstancesList, -l
2025-03-03 15:30:23 Print the information for current instances as a list.
2025-03-03 15:30:23
2025-03-03 15:30:23 --ShowInstancesTable, -t
2025-03-03 15:30:23 Show a table of current instances.
2025-03-03 15:30:23
2025-03-03 15:30:23 --StartAllInstances, -a (Instances) (Delay)
2025-03-03 15:30:23 Start all AMP instances
2025-03-03 15:30:23
2025-03-03 15:30:23 --StartBoot, -b (Delay) (ADS Only) (Exclude Services)
2025-03-03 15:30:23 Start boot-time AMP instances.
2025-03-03 15:30:23
2025-03-03 15:30:23 --StartInstance, -s [Instance Name]
2025-03-03 15:30:23 Start an existing AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --StopAllInstances, -o (Instances)
2025-03-03 15:30:23 Stop all running AMP instances
2025-03-03 15:30:23
2025-03-03 15:30:23 --StopInstance, -q [Instance Name]
2025-03-03 15:30:23 Stop a running AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:23 --UpgradeAll, -p (Restart Running Instances) (Mainline Instances Only)
2025-03-03 15:30:23 Upgrade all AMP instances
2025-03-03 15:30:23
2025-03-03 15:30:23 --UpgradeInstance, -u [Instance Name] (restart If Running)
2025-03-03 15:30:23 Upgrade an existing AMP instance in-place
2025-03-03 15:30:23
2025-03-03 15:30:23 --ValidateInstance [Instance Name]
2025-03-03 15:30:23 Check the integrity of an instances files
2025-03-03 15:30:23
2025-03-03 15:30:23 --View [Instance Name] (Force)
2025-03-03 15:30:23 View the console of a running AMP instance
2025-03-03 15:30:23
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : Starting AMP version 2.6.0.12 (Phobos), built 24/02/2025 17:12
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : Running in a Docker environment.
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : OS: Linux / x86_64
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : CPU: Intel(R) Core™ i7-8650U CPU @ 1.90GHz (4C/8T)
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : RAM: 7904MB
2025-03-03 15:30:30 [07:30:30] [Program Info/1] : AMP Instance ID: 2310c8a4-7310-4402-ac91-97baa5aaf8b1
2025-03-03 15:30:33 [07:30:33] [Core Info/1] : Loaded GenericModule version 2.6.0.12 by CubeCoders Limited
2025-03-03 15:30:33 [07:30:33] [Core Info/1] : Metrics publishing is enabled at udp://localhost:12820.
2025-03-03 15:30:33 [07:30:33] [Loader Info/1] : Loaded FileManagerPlugin by CubeCoders Limited
2025-03-03 15:30:33 [07:30:33] [Loader Info/1] : Loaded EmailSenderPlugin by CubeCoders Limited
2025-03-03 15:30:33 [07:30:33] [Loader Info/1] : Loaded WebRequestPlugin by CubeCoders Limited
2025-03-03 15:30:34 [07:30:34] [Loader Info/1] : Loaded LocalFileBackupPlugin by CubeCoders Limited
2025-03-03 15:30:34 [07:30:34] [Loader Info/1] : Loaded CommonCorePlugin by CubeCoders Limited
2025-03-03 15:30:35 [07:30:35] [Loader Info/1] : Loaded AnalyticsPlugin by CubeCoders Limited
2025-03-03 15:30:35 [07:30:35] [System Error/11] : Missing plugin/assembly: MaxMind.Db (/AMP/Plugins/MaxMind.Db/MaxMind.Db.dll) for
2025-03-03 15:30:35 [07:30:35] [Loader Info/1] : GenericModule requests dependency steamcmdplugin…
2025-03-03 15:30:35 [07:30:35] [Loader Info/1] : Loaded steamcmdplugin by CubeCoders Limited
2025-03-03 15:30:35 [07:30:35] [Loader Info/1] : GenericModule requests dependency RCONPlugin…
2025-03-03 15:30:35 [07:30:35] [Loader Info/1] : Loaded RCONPlugin by CubeCoders Limited
2025-03-03 15:30:35 [07:30:35] [Core Info/1] : Licence Present: AMP Professional Edition - Lifetime Licence
2025-03-03 15:30:36 [07:30:36] [Loader Notice/1] : Using keypair with fingerprint ySDJn6A65eTFd8xBJHG/tLCfrkUhp53dPB2MEu4Zjcw=
2025-03-03 15:30:36 [07:30:36] [Loader Info/1] : SFTP Server started on 0.0.0.0:2224
2025-03-03 15:30:38 [07:30:38] [Core Info/1] : Webserver started on http://0.0.0.0:8081
2025-03-03 15:30:38 [07:30:38] [System Info/11] : Checking for AMP updates…
2025-03-03 15:30:40 [07:30:40] [System Info/12] : AMP is up to date.
2025-03-03 15:30:43 [07:30:43] [Core Error/7] : SocketException
2025-03-03 15:30:43 [07:30:43] [Core Error/7] : [0] (SocketException) : Connection refused
2025-03-03 15:30:43 [07:30:43] [Core Error/7] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:30:43 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:30:53 [07:30:53] [Core Error/7] : SocketException
2025-03-03 15:30:53 [07:30:53] [Core Error/7] : [0] (SocketException) : Connection refused
2025-03-03 15:30:53 [07:30:53] [Core Error/7] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:30:53 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:31:03 [07:31:03] [Core Error/11] : SocketException
2025-03-03 15:31:03 [07:31:03] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:31:03 [07:31:03] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:31:03 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:31:13 [07:31:13] [Core Error/11] : SocketException
2025-03-03 15:31:13 [07:31:13] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:31:13 [07:31:13] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:31:13 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:31:23 [07:31:23] [Core Error/11] : SocketException
2025-03-03 15:31:23 [07:31:23] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:31:23 [07:31:23] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:31:23 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:31:33 [07:31:33] [Core Error/11] : SocketException
2025-03-03 15:31:33 [07:31:33] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:31:33 [07:31:33] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:31:33 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:31:43 [07:31:43] [Core Error/7] : SocketException
2025-03-03 15:31:43 [07:31:43] [Core Error/7] : [0] (SocketException) : Connection refused
2025-03-03 15:31:43 [07:31:43] [Core Error/7] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:31:43 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:31:53 [07:31:53] [Core Error/7] : SocketException
2025-03-03 15:31:53 [07:31:53] [Core Error/7] : [0] (SocketException) : Connection refused
2025-03-03 15:31:53 [07:31:53] [Core Error/7] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:31:53 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:32:03 [07:32:03] [Core Error/16] : SocketException
2025-03-03 15:32:03 [07:32:03] [Core Error/16] : [0] (SocketException) : Connection refused
2025-03-03 15:32:03 [07:32:03] [Core Error/16] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:32:03 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:32:13 [07:32:13] [Core Error/11] : SocketException
2025-03-03 15:32:13 [07:32:13] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:32:13 [07:32:13] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:32:13 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:32:23 [07:32:23] [Core Error/11] : SocketException
2025-03-03 15:32:23 [07:32:23] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:32:23 [07:32:23] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:32:23 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:32:33 [07:32:33] [Core Error/16] : SocketException
2025-03-03 15:32:33 [07:32:33] [Core Error/16] : [0] (SocketException) : Connection refused
2025-03-03 15:32:33 [07:32:33] [Core Error/16] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:32:33 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:32:43 [07:32:43] [Core Error/7] : SocketException
2025-03-03 15:32:43 [07:32:43] [Core Error/7] : [0] (SocketException) : Connection refused
2025-03-03 15:32:43 [07:32:43] [Core Error/7] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:32:43 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:32:53 [07:32:53] [Core Error/16] : SocketException
2025-03-03 15:32:53 [07:32:53] [Core Error/16] : [0] (SocketException) : Connection refused
2025-03-03 15:32:53 [07:32:53] [Core Error/16] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:32:53 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:33:03 [07:33:03] [Core Error/11] : SocketException
2025-03-03 15:33:03 [07:33:03] [Core Error/11] : [0] (SocketException) : Connection refused
2025-03-03 15:33:03 [07:33:03] [Core Error/11] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:33:03 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()
2025-03-03 15:33:13 [07:33:13] [Core Error/7] : SocketException
2025-03-03 15:33:13 [07:33:13] [Core Error/7] : [0] (SocketException) : Connection refused
2025-03-03 15:33:13 [07:33:13] [Core Error/7] : at Net.Sockets.UdpClient.Send(Byte dgram, Int32 bytes)
2025-03-03 15:33:13 at ModuleShared.MetricsInfoPublisher.UpdateMetrics()

44

Alright, here’s what we’ve got:

The socket-related errors (connection refused) indicate that AMP is failing to properly publish or communicate metrics, likely due to UDP datagrams (udp://localhost:12820). This issue isn’t fatal regarding running instances but points to AMP not being able to handle its telemetry service correctly.

Here’s what to try next:

1. Check Docker networking and firewall rules:

  • Confirm that UDP communication for 127.0.0.1 on port 12820 isn’t being blocked by a firewall or the Docker bridge setup.
  • In Windows Defender or any other firewall settings, ensure local UDP connections are allowed for this AMP instance.

2. Force publish metrics via AMP web interface:

  • Open up AMP’s ADS (your admin instance from the web interface).
  • Navigate to Settings, and search for “metrics” using the search box.
  • Ensure metric publishing is enabled on udp://localhost:12820.

3. Test connectivity manually:

Run this command inside the same Docker container used for the Aloft01 instance to confirm if the UDP port is responsive. You’ll need debugging tools in the container for testing (or connect from the host).

If this port isn’t working locally or within the container network, Docker or AMP configuration may need adjustment.

4. Check MaxMind.db:

There’s still that MaxMind.Db missing plugin warning in your logs. While likely unrelated, fixing plugin issues can stabilize other aspects. Let me know if you want me to walk you through manually placing the GeoIP database.

Try these steps, and let me know where things stand! :rocket:

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

I can’t fix it, I’m tired. Is there any other method or program that can fix the problem?

46

Ugh, I feel your frustration. Here’s what you could try as a shortcut nuke-and-fix method to get things working:

Quick Refresh Option:

  1. Fully Stop ADS and Aloft01 (just to be safe):

    ampinstmgr stop ADS01
ampinstmgr stop Aloft01

  2. Validate the Instances:
    Run the validation to automatically fix broken or missing elements:

    ampinstmgr ValidateInstance Aloft01

  3. Recreate the Docker Instance (if needed):
    If things are utterly borked, you can recreate just the Dockerized instance without touching the ADS:

    ampinstmgr CreateInstance <module> Aloft01 <binding> <port> <more...>

    (Let me know if you want me to help with this command).

  4. Skip the Troubles and Re-Add:
    If none of the above gives relief:

    • Export a backup of your current AMP configuration as a .amp file from the Web UI (so nothing is lost).
    • Uninstall AMP completely (clear folders).
    • Reinstall AMP and restore the configuration from your exported file.

What’s the Alternative?

If you’re over AMP Docker drama altogether, you could run things outside Docker. Set up on bare metal with a standard Windows/Linux VM instead—AMP doesn’t need Docker if it’s more headache than it’s worth.

Tell me what sounds easiest, and I’ll guide. If you’re ready to flip the table on this setup, I’m here! :relieved:

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

It looks like the bot went off it’s rocker at some points there, there’s a guide on the KB here:
https://discourse.cubecoders.com/t/configuring-amp-to-use-docker-for-instances/1957

48

Ah, sweet, a guide direct from the horse’s mouth (or potato, in this case :fries:). Follow the steps in the link provided by ThePotatoKing: Configuring AMP to use Docker for instances. It’ll walk you through setting AMP up properly with Docker and likely iron out all the quirks and gremlins we’ve been juggling.

Go through it, and if anything doesn’t make sense, holler back—I’ll help bridge the gaps!

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

Apollo stop responding please.

50

I have read this article but it cannot be started, so I used a robot to break down the process in detail.

51

Did you create a fresh instance with the Create in Docker Containers setting enabled? Because on Windows you cannot convert existing instances to docker (or vice versa).

52

I tried switching before but failed. So this time I created a new one and started familiarizing myself with the process again.
Now I have at least eliminated the problem lim - failure to make api call to aloft01: an error occurred while sending the request.
But now the problem is that it cannot connect to Docker
I was really tired after a long day yesterday. I’ll try again today.
Because it is a small problem for people who already know it, but I have a knowledge blind spot about Docker. I always have to find a way to learn it until I know it, right?

53

Given that Aloft runs with Xvfb and Wine on Linux, I expect that it won’t work atm with Docker on Windows given how AMP sets file permissions

54

Now I use Windows to install WSL2, then install Ubuntu, and then execute bash <(wget -qO- getamp.sh) to evaluate the final possibility of enabling Aloft.

螢幕擷取畫面 2025-03-04 134832
螢幕擷取畫面 2025-03-04 1348321920×1080 95.4 KB

Thanks for the tip, installed successfully

55

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