Differences

This shows you the differences between two versions of the page.

--- wiki:docker_troubleshooting [2025/04/10 12:25] – [Containers lose access to internet suddenly] update docker version antisa
+++ wiki:docker_troubleshooting [2026/10/14 08:24] (current) – add unexpected EOF antisa
@@ Line 139: / Line 139: @@
 ==== Tested on ====
   * Debian 11
+===== docker-compose down default_network error =====
+Try running compose down with exact same compose files as when the containers where created so if the containers were created like this:
+  # docker compose -f compose.database.yml -f compose.nats.yml -f compose.yml up -d
+Run this:
+  # docker compose -f compose.database.yml -f compose.nats.yml -f compose.yml down
+A simple ''docker compose down'' in the same directory will result in above error.
+===== network ... does not exist =====
+<code | download>
+'Error starting container 433f85f4bdf20d81c2f1c5ea5732e598d5ec0b7ea40e373d2e7a04fdff1b70d3:
+Server Error for http+docker://localhost/v1.55/containers/433f85f4bdf20d81c2f1c5ea5732e598d5ec0b7ea40e373d2e7a04fdff1b70d3/start:
+        Internal Server Error ("failed to set up container networking: failed to create
+        endpoint <container_name> on network <network_name>: network 979026f0e39e821207f8070a704fa949e31ed0742b1f06348da7540b5c785e13
+        does not exist")'
+</code>
+Delete the network <network_name> mentioned in the message.
+  docker network rm <network_name>
+===== unexpected EOF  =====
+Sometimes happens due to network issues but the problem also manifested when trying to pull an image from a private repository where one of the layers was missing. You'll see something like
+```
+eb75867ef: Pull complete
+a64644b756: Pull complete
+c2ddfd6010: Downloading [============================================>      ]  13.93MB/15.52MB
+bfe8972e2: Retrying in 1 second
+eb9fa6c40ea7: Downloading [=====>                                             ]  26.49MB/224.7MB
+```
+If it works on one machine and not on the other it could be due to docker cache. Try clearing entire cache with `docker system prune -a` and see if the problem occurs on the machine where it works.
+The fix in this case was to run `docker build` and push the new image to repo, after cache has been cleaned.
 ====== See also ======