Image: imvickykumar999/warzone
The container runs:
| Service | Port | Role |
|---|---|---|
bridge.py | 8080 | Web client (open this in the browser) |
bridge.py | 8765 | WebSocket bridge (browser ↔ game server) |
server.py | 8888 | TCP game server |
docker pull imvickykumar999/warzone:latest
Expose all three ports:
docker run -d --name warzone \
-p 8080:8080 \
-p 8765:8765 \
-p 8888:8888 \
imvickykumar999/warzone:latest
Useful commands:
docker logs -f warzone # watch startup logs
docker stop warzone # stop
docker start warzone # start again
docker rm -f warzone # remove container
Open the web client on port 8080. That is the URL players use.
| Where you play | URL |
|---|---|
| Same machine | http://localhost:8080 |
| Phone / other device on same Wi‑Fi | http://<YOUR_LAN_IP>:8080 |
Find your LAN IP:
ipconfig → look for IPv4 (e.g. 192.168.1.10)hostname -I or ip addrExample: http://192.168.1.10:8080
| Where you play | URL |
|---|---|
| Anyone on the internet | http://<VPS_PUBLIC_IP>:8080 |
Example: http://203.0.113.45:8080
On the VPS firewall / cloud security group, allow inbound TCP:
docker pull imvickykumar999/warzone:latest8080, 8765, 8888http://localhost:8080 (laptop) or http://<public-or-lan-ip>:8080 (VPS / LAN)Content type
Image
Digest
sha256:ec4aff3e2…
Size
136.6 MB
Last updated
23 days ago
docker pull imvickykumar999/warzone