docs: Use host networking as default for Docker

DHCP/TFTP need direct network access for PXE boot — port forwarding
doesn't work for broadcast protocols. Host networking is the only
correct configuration.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: Zorlin

content/docs/installation/docker.md

@@ -17,8 +17,7 @@ services:
   dragonfly:
     image: ghcr.io/riffcc/dragonfly:latest
     restart: unless-stopped
-    ports:
-      - "3000:3000"
+    network_mode: host
     volumes:
       - dragonfly-data:/var/lib/dragonfly
     environment:
@@ -34,38 +33,9 @@ Then run:
 docker compose up -d
 ```
 
-Visit the web interface at `http://localhost:3000`
-(or `http://your-hostname:3000` if you're not running it locally).
-
-### Networking for PXE boot
-
-The default port-forwarded configuration works for the web UI and basic management. If you need PXE boot functionality (DHCP and TFTP), you'll need host networking:
+Visit the web interface at `http://your-hostname:3000`.
 
-```yaml
-services:
-  dragonfly:
-    image: ghcr.io/riffcc/dragonfly:latest
-    restart: unless-stopped
-    network_mode: host
-    volumes:
-      - dragonfly-data:/var/lib/dragonfly
-    environment:
-      - RUST_LOG=info
-
-volumes:
-  dragonfly-data:
-```
-
-Host networking is required because DHCP uses broadcast packets and TFTP requires direct socket access, which don't work through Docker's port forwarding.
-
-### Customising the port
-
-To run on a different port, change the port mapping:
-
-```yaml
-    ports:
-      - "8080:3000"  # Access on port 8080 instead
-```
+Host networking is required because Dragonfly's DHCP and TFTP services need direct access to the network for PXE boot functionality.
 
 ### Data persistence
 

content/docs/installation/quick-start.md

@@ -19,8 +19,7 @@ services:
   dragonfly:
     image: ghcr.io/riffcc/dragonfly:latest
     restart: unless-stopped
-    ports:
-      - "3000:3000"
+    network_mode: host
     volumes:
       - dragonfly-data:/var/lib/dragonfly
     environment: