Icarus Docker instance does not create GamePort (UDP 17777) firewall rule

Technical Support
,
1

Environment:

  • Debian 12 host
  • AMP v2.6.3.x Mainline
  • Icarus instance running in Docker mode
  • UFW active (AMP auto-managing firewall rules)

Issue:
When creating and starting a new Icarus instance in Docker mode, AMP only creates the QueryPort.
The GamePort (UDP 17777) is not added automatically to firewall rules.

Expected behavior:
AMP should register GamePort similar to other game modules (e.g., Minecraft, Enshrouded).

Steps to reproduce:

  1. Create new Icarus instance with Docker mode enabled
  2. Start the instance
  3. Check firewall rules — only QueryPort is registered, GamePort 17777/udp missing

Additional Notes:
Other game modules behave correctly — issue appears specific to Icarus + Docker mode.

2

It actually doesn’t matter since the game uses Steam networking and so a socket isn’t opened on the game port

But yes, amp should be create fw rules for all allocated ports. What you have observed is not normal

Is your ampinstmgr up to date? Check with ampinstmgr version

3

AMP Instance Manager v2.6.3.2 (Mainline)

Here is the current behavior:

  • Allocated ports exist in the Icarus template (GamePort 17777/udp, QueryPort)

  • But the container publishes no ports at all

Output:

docker ps --format ‘table {{.Names}}\t{{.Ports}}’ | grep -i icarus
AMP_AMPBerlinIcarus01

Inspect also shows no HostConfig.PortBindings for 17777/udp:

docker inspect --format ‘{{json .HostConfig.PortBindings}}’ AMP_AMPBerlinIcarus01
null

I understand that Icarus uses Steam Networking and doesn’t open a socket on the GamePort, but AMP should still create firewall rules for all allocated ports.
This only happens with Icarus — other game instances create their firewall rules correctly.

Let me know if you need logs or a debug build — happy to test.

Thanks!