OS Name/Version:
Debian VM (Running inside ZimaOS Docker environment)
Product Name/Version:
AMP v2.7.2.8
Problem Description:
Hey guys, I’m having a weird Docker networking issue with my Garry’s Mod 64Bit instance.
The main problem is that AMP’s “Application IP Binding” dropdown completely refuses to show my current, correct VM IP (192.168.178.88). It only lists an old, outdated IP (.85) and the invalid “::” or “0.0.0.0” selections.
When I try to deploy or start the instance using 0.0.0.0, the container immediately crashes with Error Code 125. The console log says:
Error: invalid port format - format is [[hostIP:]hostPort:]containerPort
Failed to configure new instance GarrysMod64Bit01 - Startup failure: Error code 125.
It seems AMP is generating a broken port string because it can’t resolve the correct IP binding, which causes Docker to choke. Even newly created instances inherit this exact same broken behavior.
Steps to reproduce:
- Step 1: Create a fresh Garry’s Mod instance.
- Step 2: Open “Network and Ports” – notice that the actual host IP (.88) is missing from the dropdown, only an old IP (.85) is visible.
- Step 3: Hit Update or Start using the default binding, which immediately triggers the Error 125 port format crash.
Actions taken to resolve so far:
- Completely purged unused Docker networks and containers via terminal (
docker system prune -f). - Manually changed
UseHostNetworking=Trueand adjusted the IP binding insideAMPConfig.conffor both the instance and ADS01. - Re-created the instance from scratch.
- Restarted the AMP service (
ampinstmgr.service) multiple times.
None of this worked, AMP keeps falling back to the broken port format. Any ideas how to force AMP to refresh its network interfaces cache?