Closed PrawnMan closed 4 years ago
You have to keep the port of the container the same and change the exposed port
docker run -d --name 7Eleven_Fuel_2 -p 5001:5000 fuellock
As the port is not changed in the container
You have to keep the port of the container the same and change the exposed port
docker run -d --name 7Eleven_Fuel_2 -p 5001:5000 fuellock
As the port is not changed in the container
That's what I was doing incorrectly. Cheers for correcting me. Tried it and it works perfectly now.
EDIT: Sorry, I dont know how to close this or mark it as resolved?
close #50
Aim : Run Concurrent Containers to allow multiple LAN users to use my server. Methodology: Previously installed application via docker as per readme. Issued command to run the first server as per instruction:
Docker launches application and web interface is available on serverIp:5000 as expected.
Then I try to run a second concurrent instance on a different port:
docker run -d --name 7Eleven_Fuel_2 -p 5001:5001 fuellock
Terminal reports that the program is running.
Expected outcome: Webpage accessible on serverip:5001
Actual outcome: I try to access the web interface on serverip:5001.
The page does not display showing "ERR_CONNECTION_REFUSED"
Output from terminal at this point:
.
Host: Linux ionic 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux