November 18, 20241 yr Hi all, JorgeB help me get my docker image rebuilt but now I have a different issue. Before installing al my applications I made a custom docker network called the-arrs that I use to run my media applications so they run in there own network. Now that the containers are running all but one or two have an IP address and I can't connect to them. Anyone have any ideas whats going on and how I can fix this.
November 19, 20241 yr Community Expert run in termal docker network ls and docker inspect network the-arrs we may need to remove the docker network and recreate it
November 20, 20241 yr Author Hi bartino, the result of running docker network ls root@Locutus:~# docker network ls NETWORK ID NAME DRIVER SCOPE 4eb6e48fe60b br0 ipvlan local 4974d5e68b6a bridge bridge local c23f590356ad host host local 9d85fee46172 none null local 781daf242b17 the-arrs bridge local root@Locutus:~# and now docker inspect network the-arrs root@Locutus:~# docker inspect network the-arrs [ { "Name": "the-arrs", "Id": "781daf242b174d8022d621313fdf7343d7b63a93e5b8de2aa790c2e1eccb28a8", "Created": "2024-11-16T13:23:48.915916839Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.19.0.0/16", "Gateway": "172.19.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "337973fe3bac029155e79631848b04dee6ae3d441a5fabbea187f24ce11c0aec": { "Name": "prowlarr", "EndpointID": "1ba201437c5be293706424bb4fb67e60dcd7bc17a84987ea35c4a0baae61aa63", "MacAddress": "02:42:ac:13:00:03", "IPv4Address": "172.19.0.3/16", "IPv6Address": "" }, "9209317f760a9aa9fd69e8b1aab73472bd71ac8ce499c896f89843e555bbfe29": { "Name": "radarr", "EndpointID": "1686a7f67091ace56dfbf03a3968eda60ad9766b4d508ed2bb1cd37e2d1b8248", "MacAddress": "02:42:ac:13:00:04", "IPv4Address": "172.19.0.4/16", "IPv6Address": "" }, "c7172ee53700618f540ed19859ff07635ffa1c3e42ed198467647052035c8bbb": { "Name": "lidarr", "EndpointID": "ff85813ae4d9bc1e8d0d760ccc9caa1c3bde582d79a6502bd96e0ae94f593aa2", "MacAddress": "02:42:ac:13:00:02", "IPv4Address": "172.19.0.2/16", "IPv6Address": "" } }, "Options": {}, "Labels": {} } ] Error: No such object: network Thanks for your help with this.
November 20, 20241 yr I suspect it has to do with the "none" and it having a "null" network. Not sure how it was created but default if you do something like "docker network create the_arrs" is bridge. just did it here. Quote ef113f8feb4b the_arrs bridge local Id create the network and point the container to it Looked at my configuration and none is something already setup by Unraid/Docker, so you just need to change your network off it to get an IP Edited November 20, 20241 yr by stayupthetree
November 21, 20241 yr Community Expert Thank you. It seems like your the-arrs Docker network is either misconfigured or corrupted. Here’s a step-by-step guide to remove and recreate the network for proper functionality. Step 1: Inspect the Current Network Run the following to see which containers are connected to the the-arrs network: docker network inspect the-arrs From your output, the following containers are attached: prowlarr radarr lidarr we can try to reuse and check the dockers to recoennnet... Step 2: Disconnect Containers Disconnect the containers from the-arrs to avoid conflicts: docker network disconnect the-arrs prowlarr docker network disconnect the-arrs radarr docker network disconnect the-arrs lidarr Verify the containers are no longer attached: docker network inspect the-arrs Step 3: Remove the Broken Network Remove the corrupted network: docker network rm the-arrs If you see an error such as Error: No such object: network, ensure no containers are still connected and retry. Step 4: Recreate the Network Now, recreate the the-arrs network. For a basic bridge network setup: docker network create \ --driver bridge \ --subnet=172.19.0.0/16 \ the-arrs You can also modify the configuration if needed (e.g., enabling IPv6 or setting specific options). examples in docs: https://docs.docker.com/reference/cli/docker/network/create/ Step 6: Verify the Setup Ensure the network and containers are properly configured: docker network inspect the-arrs docker ps Optional: Use Custom Static IPs If you need static IPs for the containers, you can specify them when connecting: docker network connect --ip 172.19.0.10 the-arrs prowlarr docker network connect --ip 172.19.0.11 the-arrs radarr docker network connect --ip 172.19.0.12 the-arrs lidarr Be sure to edit each docker in Unrad web UI and make sure the netowrk is set to the correct netowrk... Other Common Troubleshooting Network Still Failing to Delete: Stop docker start docker - restart Unraid... Network Conflicts: Ensure no other networks overlap with 172.19.0.0/16.
November 21, 20241 yr Author Hi bmartino1, After very carefully following your guide to step 6 this is the situation I find my self in. With the containers running even though the network is now appearing the containers are not getting an IP. I've attached my cli output showing the steps I took. binhex-sabnzbd is still having a problem with the network despite the config having the correct network, strange. root@Locutus:~# docker network disconnect the-arrs prowlarr root@Locutus:~# docker network disconnect the-arrs radarr root@Locutus:~# docker network disconnect the-arrs lidarr root@Locutus:~# docker network inspect the-arrs [ { "Name": "the-arrs", "Id": "781daf242b174d8022d621313fdf7343d7b63a93e5b8de2aa790c2e1eccb28a8", "Created": "2024-11-16T13:23:48.915916839Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.19.0.0/16", "Gateway": "172.19.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] root@Locutus:~# docker network rm the-arrs the-arrs root@Locutus:~# docker network ls NETWORK ID NAME DRIVER SCOPE 4eb6e48fe60b br0 ipvlan local 4974d5e68b6a bridge bridge local c23f590356ad host host local 9d85fee46172 none null local root@Locutus:~# docker network create \ > --driver bridge \ > --subnet=172.19.0.0/16 \ > the-arrs ff54bf2796fe949fcc49124e6259b89caa3a9ef31c3aa9f26af6a4e4d16f0b8f root@Locutus:~# docker network inspect the-arrs [ { "Name": "the-arrs", "Id": "ff54bf2796fe949fcc49124e6259b89caa3a9ef31c3aa9f26af6a4e4d16f0b8f", "Created": "2024-11-21T11:35:26.223788051Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.19.0.0/16" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] root@Locutus:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bb703c44083a amir20/dozzle "/dozzle" 31 hours ago Up 10 hours 0.0.0.0:8085->8080/tcp, :::8085->8080/tcp Dozzle 7c6c0b758afa lscr.io/linuxserver/homeassistant "/init" 31 hours ago Up 10 hours Home-Assistant 3fabd2296c29 jlesage/mediainfo "/init" 2 days ago Up 10 hours 0.0.0.0:7817->5800/tcp, :::7817->5800/tcp, 0.0.0.0:7917->5900/tcp, :::7917->5900/tcp MediaInfo 0e8f497546bc mikenye/picard "/init" 3 days ago Up 7 minutes 0.0.0.0:5800->5800/tcp, :::5800->5800/tcp, 5900/tcp MusicBrainz-Picard d1c398636e7b clamav/clamav "/init" 3 days ago Up 10 hours (healthy) 0.0.0.0:3310->3310/tcp, :::3310->3310/tcp, 7357/tcp ClamAV 2fb3c6591525 plexinc/pms-docker "/init" 4 days ago Up 3 days Plex-Media-Server 001aa28cca90 securecompliance/gvm:11.0.1-r3 "/bin/sh -c '/start.…" 4 days ago Up 10 hours 0.0.0.0:8088->9392/tcp, :::8088->9392/tcp frak-gvm 24458a4d2933 binhex/arch-krusader "/usr/bin/dumb-init …" 4 days ago Up 10 hours 5900/tcp, 0.0.0.0:6080->6080/tcp, :::6080->6080/tcp binhex-krusader d11a68f18fe2 ghcr.io/recyclarr/recyclarr:latest "/sbin/tini -- /entr…" 4 days ago Up 10 hours recyclarr 1fc6c5bc70e1 jlesage/qdirstat "/init" 4 days ago Up 10 hours 0.0.0.0:7815->5800/tcp, :::7815->5800/tcp, 0.0.0.0:7915->5900/tcp, :::7915->5900/tcp QDirStat 9ed27c22c1df ghcr.io/home-assistant-libs/python-matter-server:stable "matter-server --sto…" 4 days ago Up 10 hours matter-server 3023f45d5b67 ich777/luckybackup "/opt/scripts/start.…" 4 days ago Up 10 hours 0.0.0.0:8086->8080/tcp, :::8086->8080/tcp luckyBackup 5109a81c570d jbartlett777/diskspeed "catalina.sh run" 4 days ago Up 10 hours 8080/tcp, 0.0.0.0:18888->8888/tcp, :::18888->8888/tcp DiskSpeed 763aeb21b35c jlesage/czkawka "/init" 4 days ago Up 10 hours 0.0.0.0:7821->5800/tcp, :::7821->5800/tcp, 0.0.0.0:7921->5900/tcp, :::7921->5900/tcp Czkawka 93aae5cb1024 lscr.io/linuxserver/airsonic-advanced "/init" 4 days ago Up 10 hours 0.0.0.0:4040->4040/tcp, :::4040->4040/tcp airsonic-advanced root@Locutus:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bb703c44083a amir20/dozzle "/dozzle" 31 hours ago Up 10 hours 0.0.0.0:8085->8080/tcp, :::8085->8080/tcp Dozzle 9209317f760a ghcr.io/hotio/radarr:latest "/init" 31 hours ago Up 3 minutes radarr 337973fe3bac ghcr.io/hotio/prowlarr "/init" 31 hours ago Up 5 minutes prowlarr 7c6c0b758afa lscr.io/linuxserver/homeassistant "/init" 31 hours ago Up 10 hours Home-Assistant 3fabd2296c29 jlesage/mediainfo "/init" 2 days ago Up 10 hours 0.0.0.0:7817->5800/tcp, :::7817->5800/tcp, 0.0.0.0:7917->5900/tcp, :::7917->5900/tcp MediaInfo 0e8f497546bc mikenye/picard "/init" 3 days ago Up 14 minutes 0.0.0.0:5800->5800/tcp, :::5800->5800/tcp, 5900/tcp MusicBrainz-Picard d1c398636e7b clamav/clamav "/init" 3 days ago Up 10 hours (healthy) 0.0.0.0:3310->3310/tcp, :::3310->3310/tcp, 7357/tcp ClamAV 2fb3c6591525 plexinc/pms-docker "/init" 4 days ago Up 3 days Plex-Media-Server c7172ee53700 ghcr.io/hotio/lidarr:latest "/init" 4 days ago Up 4 minutes lidarr 001aa28cca90 securecompliance/gvm:11.0.1-r3 "/bin/sh -c '/start.…" 4 days ago Up 10 hours 0.0.0.0:8088->9392/tcp, :::8088->9392/tcp frak-gvm 24458a4d2933 binhex/arch-krusader "/usr/bin/dumb-init …" 4 days ago Up 10 hours 5900/tcp, 0.0.0.0:6080->6080/tcp, :::6080->6080/tcp binhex-krusader f3790ad35636 ghcr.io/hotio/sonarr:latest "/init" 4 days ago Up 3 minutes sonarr d11a68f18fe2 ghcr.io/recyclarr/recyclarr:latest "/sbin/tini -- /entr…" 4 days ago Up 10 hours recyclarr 1fc6c5bc70e1 jlesage/qdirstat "/init" 4 days ago Up 10 hours 0.0.0.0:7815->5800/tcp, :::7815->5800/tcp, 0.0.0.0:7915->5900/tcp, :::7915->5900/tcp QDirStat 9ed27c22c1df ghcr.io/home-assistant-libs/python-matter-server:stable "matter-server --sto…" 4 days ago Up 10 hours matter-server 3023f45d5b67 ich777/luckybackup "/opt/scripts/start.…" 4 days ago Up 10 hours 0.0.0.0:8086->8080/tcp, :::8086->8080/tcp luckyBackup 5109a81c570d jbartlett777/diskspeed "catalina.sh run" 4 days ago Up 10 hours 8080/tcp, 0.0.0.0:18888->8888/tcp, :::18888->8888/tcp DiskSpeed 763aeb21b35c jlesage/czkawka "/init" 4 days ago Up 10 hours 0.0.0.0:7821->5800/tcp, :::7821->5800/tcp, 0.0.0.0:7921->5900/tcp, :::7921->5900/tcp Czkawka 93aae5cb1024 lscr.io/linuxserver/airsonic-advanced "/init" 4 days ago Up 10 hours 0.0.0.0:4040->4040/tcp, :::4040->4040/tcp airsonic-advanced root@Locutus:~#
November 21, 20241 yr Community Expert https://docs.unraid.net/unraid-os/manual/docker-management/ you will need to stop all dockers using the network the point is to get the system ready to remove that network for recreation. This may be include removing the dockers... (DO NOT REMOVE IMAGE!) to get to the point where we can recreate the dockers and reconnect it to the network... a system reboot may also be need after doing this... You may also need to delete the docker db file... as seen here: *This will remove all docker networks as well... Based on your output and description, it seems the issue is related to the containers not properly receiving an IP address when connected to the newly created custom Docker network (the-arrs). Here's a step-by-step diagnostic and potential solutions: *^ - Assumes you removed the network.. and successfully recreated it... Recommend watch: So Diagnostic: Why Aren't Containers Getting an IP Address? Network Configuration Issue: Check the Docker network settings to ensure the subnet and gateway are correctly configured and do not conflict with other networks. Verify no other containers or networks are using the 172.19.0.0/16 range. Docker Container Settings: Ensure each container is configured to use the the-arrs network. Verify the containers are not set to "host" or "bridge" mode if they should be using the-arrs. IPAM Configuration Issue: The IP Address Management (IPAM) settings for the-arrs might not be assigning IPs correctly. This can happen due to misconfigured options or overlapping subnets. Docker Daemon Restart: Sometimes, changes to Docker networks require restarting the Docker service or even the host system to apply fully. Container Connectivity: Run docker network inspect the-arrs and confirm that containers are listed under the Containers section with appropriate IPs. You need to remove the netwok and recreate it! ... Recommended Solutions Turn off any and all autostarts... then setting > docker Turn off... Then recreate network by remvoing netwrok, db file and rebooting unraid. (May need to turn docker on) Create network *IT IS IMPROTANT TO NOT HAAVE ANY AUTOSTART... as we will be editing that latter... I would recomend moving to macvlan as well... You mainly want to have the above option IPvlan is fine... Then follwing the steps... 1. Recreate the Docker Network with Correct Settings docker network rm the-arrs rm /var/lib/docker/network/files/local-kv.db #Reboot #create docker network... docker network create \ --driver bridge \ --subnet=172.19.0.0/16 \ the-arrs *restart docker services: /etc/rc.d/rc.docker restart Edited November 21, 20241 yr by bmartino1
November 21, 20241 yr Community Expert I would need a docker inspect of all the netwroks. 4eb6e48fe60b br0 ipvlan local 4974d5e68b6a bridge bridge local c23f590356ad host host local 9d85fee46172 none null local 781daf242b17 the-arrs bridge local the default bridge may already have claimed the 172.19.X.X subnet...
November 26, 20241 yr Author Sorry for not keeping in contact to let you know how things are going, but real life has gotten in the way and I have been very busy. I have read through your post and watch the youtube video, very informative it's a shame he moves so quickly through each network but I can watch it again to make it stick. I did attempted to take a look yesterday but could not log on as the server had crashed, this is a persistent issue I have been having and most likely the reason the docker image became corrupted in the first place. I've had to remake the docker image several times now... Unfortunately it's intermittent and you can't predict when it will crash, JorgB has helped me recover more than a few times so thinking about that it's probably best to fix the crashing first which only started after I moved the file system from XFS to ZFS. Stated the week of the 2nd December I will be in hospital for 3 week so that means coming out just before Christmas. I do entend to fix all issue so will keep in contact.
.thumb.png.f4dc98381367516493e6f5482ac023aa.png)
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.