Startup Issue with Application Deployment - Error code 125 when starting Terraria server

legg1999 · 8 January 2025 01:47

System Information

Field	Value
Operating System	Windows - Windows 11 Pro on x86_64
Product	AMPService ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization	None
Application	Application Deployment
Module	ADSModule
Running in Container	Yes
Current State	3

Problem Description

Issue

New server fails to start when creating new Terraria server in docker desktop

Reproduction Steps

Follow guide for configuring AMP to use docker for instances: Configuring AMP to use Docker for instances
Create new Terraria server
receive error code 125

EDIT Upon looking at the console, it says:

ThePotatoKing · 8 January 2025 02:05

There’s an issue with Windows+Docker fixed in the next release:

github.com/CubeCoders/AMP

Webserver-port is included twice in the docker run command

opened 01:57AM - 01 Dec 24 UTC

closed 06:23AM - 13 Dec 24 UTC

mpuetz

bug

### Operating System Windows 11 Pro 24H2 ### AMP Version and Build Date … 2.6.0.6 - 20241120.1 ### AMP Release Stream Mainline ### I confirm that - [X] I have searched for an existing bug report for this issue. - [X] I am using the latest available version of AMP. - [X] my operating system is up-to-date. ### Intended Action Starting a docker-instance using the webinterface or creating a new docker instance. ### Expected Behaviour AMP starts the instance using the docker run command, including every needed port once in the -p command ### Actual Behaviour The webserver-port is mentioned twice in the -p part of the docker run command, causing docker to fail as it can't bind the same port twice ("port already in use"). ### Reproduction 1. Make a fresh install using AMP 2.6.0.4 according to the instructions on discourse. 2. Set everything up for running instances in docker according to the discourse article. 3. Create a new Satisfactory-instance 4. Run it, it works. 5. Upgrade to AMP 2.6.0.6 according to the discourse article for upgrading. 6. Try to start the formerly created instance or create a new instance in docker 7. Startup fails with error "docker: Error response from daemon: driver failed programming external connectivity on endpoint AMP_Satisfactory_Vanilly01_CONFIGURE (c62e56d7a3189f3c5064010a8839a297a323c8202f79eb14f170f368fe0530a0): failed to bind port 0.0.0.0:8084/tcp: listen tcp4 0.0.0.0:8084: bind: address already in use." 8. Set the logging to "debug" in the settings 9. try to start the instance again 10. AMP tries to start the instance usind the command "docker run [...] -p 8084:8084/tcp -p 2227:2227/tcp -p 7778:7778/tcp -p 7778:7778/udp -p 8084:8084/tcp [...]", where 8084 is the correct webserver port for the instance. The other ports are needed for the game. The webserver port is listed twice in the command which should not happen as it prevents docker from starting.

system · 7 February 2025 02:05

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