diff --git a/docker-compose.yml b/docker-compose.yml
index 53b1c75..e785a5c 100644
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -276,7 +276,17 @@ services:
   lazytainer:
     image: ghcr.io/vmorganp/lazytainer:master
     container_name: lazytainer
-    network_mode: host
+    # NOT network_mode: host — lazytainer identifies its own container by
+    # matching os.Hostname() against the Docker container-ID list
+    # (vmorganp/Lazytainer, configureFromLabels()); under host networking the
+    # container inherits the host's hostname instead of its own ID, so that
+    # match always fails and it panics with "Could not determine container ID
+    # of lazytainer" on every start. Host networking also can't see traffic
+    # to llama-server:8080 anyway — that port only exists on the ai-stack
+    # bridge network (no host port published, see issue #15 above). Joining
+    # ai-stack instead fixes both: hostname becomes the real container ID,
+    # and it's on the same network as the traffic it's watching.
+    networks: [ai-stack]
     volumes:
       - /var/run/docker.sock:/var/run/docker.sock:ro
     restart: unless-stopped