Menu

Self-hosted Server Panel
📰

Self-hosted Server Panel

DEV Community: docker·EpicWing·9 days ago
#V7iW9ERb
#devtodocker#devto#dev#container#limit
Reading 0:00
15s threshold

Im building EpicWing, an open source (MIT) self-hosted panel for running game servers, Discord bots, websites and other services in Docker containers. The backend is FastAPI, the frontend is Vue, and the agent that runs on each node is written in Go. It's still in beta.

In v0.2.0-beta I worked on one question: what happens when one container misbehaves? Here is what I changed and why.

1. Containers could talk to each other

All containers sat in Docker's default bridge network, and inter-container traffic is on by default there. A hacked game server could scan the ports of its neighbours.

The agent now creates a separate network at startup:

docker network create --ipv6 \ -o com.docker.network.bridge.enable_icc=false epicwing-servers

Enter fullscreen mode

Exit fullscreen mode

Containers in it still reach the internet and their published ports, but not each other.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.