RemkoLeupen Posted July 22, 2022 Share Posted July 22, 2022 (edited) Unraid Version: 6.10.3 I am running an adguard docker on a br0 192.168.178.6/24. I tried to add an ipv6 got an error IPv6 is not in the correct subnet. So I removed it again and tried to start it without the IPv6 adres. IPv4 only. then I am getting: docker: Error response from daemon: Address already in use. So I removed the whole docker and deployed is again with only IPv4, again: docker: Error response from daemon: Address already in use. there is no docker running with that IP. Tried to deploy Nextcloud on the same adres 192.168.178.6, again: docker: Error response from daemon: Address already in use. I can not deploy any dockers on ip 192.168.178.6 any-more using br0. As if IP 192.168.178.6 is locked. I did a reboot of unraid checked the docker network but 192.168.178.6 is not used any-ware. is there a file I need to reset to remove locked IP addresses. at the moment I did mess this up 10 times so I have 10 addresses i can no longer use in docker. Any tips or tricks? only running CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f0d2bd60212c nextcloud:latest "/entrypoint.sh apac…" 11 minutes ago Up 11 minutes Nextcloud 25287aef7de6 pihole/pihole:latest "/s6-init" About an hour ago Up 38 minutes (healthy) pihole fec24220a48c lscr.io/linuxserver/homeassistant "/init" 6 hours ago Up 6 hours homeassistant 35177c01cb2d emby/embyserver "/init" 3 weeks ago Up 4 days EmbyServer 86f5a175b19f analogic/poste.io "/init" 4 weeks ago Up 4 days (healthy) poste 554edbc47a81 linuxserver/unifi-controller:LTS "/init" 18 months ago Up 4 days unifi-controller root@DataServer:~# docker network ls NETWORK ID NAME DRIVER SCOPE 3837ed44b609 br0 macvlan local 903376b53ade bridge bridge local f201d058efb1 host host local 8ec1cd7308f3 none null local "Containers": { "25287aef7de6ad0f3af67ba50b67940d99bab4ca932be482e11fbec803bde615": { "Name": "pihole", "EndpointID": "43536a63ceaf483c637740455598878cbba2b1fd1d5dc12ac6362add1a0b92a5", "MacAddress": "02:42:c0:a8:b2:08", "IPv4Address": "192.168.178.8/24", "IPv6Address": "2a10:3781:17a4:1::4/64" }, "554edbc47a810f7d24ce595528d21ab2388b7481a7998ff57b0b5f3b535fbe51": { "Name": "unifi-controller", "EndpointID": "a72de6454c21f3beb051668d9d21a8001594c983562480d01e48a2cee6fafa5d", "MacAddress": "02:42:c0:a8:b2:de", "IPv4Address": "192.168.178.222/24", "IPv6Address": "2a10:3781:17a4:1::3/64" }, "86f5a175b19f19b6b6e0282f06e76bc4fd104b4ae20f21e8b4defe641aba2de2": { "Name": "poste", "EndpointID": "60a41018ba968536ae1d3ac643d132284616d25d235d59d93bd4e6673a995b8b", "MacAddress": "02:42:c0:a8:b2:7b", "IPv4Address": "192.168.178.123/24", "IPv6Address": "2a10:3781:17a4:1::2/64" }, "f0d2bd60212c244efc3fccbaf218236e262d2d9f0f8264950eeab864cf0e31b9": { "Name": "Nextcloud", "EndpointID": "413161f28b1ca67dbb9563f15c72a7a1a38bd3054f90c017a65572a8ee9cb032", "MacAddress": "02:42:c0:a8:b2:79", "IPv4Address": "192.168.178.121/24", "IPv6Address": "2a10:3781:17a4:1::6/64" }, "fec24220a48cc5bc3dfa42753854b70485c060d0245f54febd46d0bb8b802ab9": { "Name": "homeassistant", "EndpointID": "4fc4abca99d97eb3662c469233393ead00417b84e12410fa1973f1e9d788c865", "MacAddress": "02:42:c0:a8:b2:85", "IPv4Address": "192.168.178.133/24", "IPv6Address": "2a10:3781:17a4:1::5/64" } dataserver-diagnostics-20220722-1657.zip Edited July 23, 2022 by RemkoLeupen Quote Link to comment
Vr2Io Posted July 23, 2022 Share Posted July 23, 2022 12 hours ago, RemkoLeupen said: "Containers": { "25287aef7de6ad0f3af67ba50b67940d99bab4ca932be482e11fbec803bde615": { "Name": "pihole", "EndpointID": "43536a63ceaf483c637740455598878cbba2b1fd1d5dc12ac6362add1a0b92a5", "MacAddress": "02:42:c0:a8:b2:08", "IPv4Address": "192.168.178.6/24", "IPv6Address": "2a10:3781:17a4:1::4/64" }, Pihole using that IP. Quote Link to comment
RemkoLeupen Posted July 23, 2022 Author Share Posted July 23, 2022 My bad. it should be 192.168.178.8. I picked the wrong output. Quote Link to comment
Squid Posted July 23, 2022 Share Posted July 23, 2022 Have you tried a reboot yet? Quote Link to comment
Solution RemkoLeupen Posted July 25, 2022 Author Solution Share Posted July 25, 2022 (edited) multiple times. is there a config file of something like that where docker stores its used ip adresses? After rebooting in save mode. removing all PiHole settings and docker. started in normal mode. deployed PiHole again. an now I can assign the original address. I have no idea what happened Edited July 25, 2022 by RemkoLeupen Quote Link to comment
Smakodak Posted September 4, 2022 Share Posted September 4, 2022 (edited) Since I ran into the same problem and since a part of the post that is marked as a solution is containing the phrase "I have no idea what happened", I'm reopening this thread rather than starting a new. If this is considered out of line, please let me know. I have numerous vlans all configured like this: 10.0.50.x/28 where x is the second last address in range and the last address is gateway. So my first vlan is 50 and is configured like this: IP: 10.0.50.13/28 GW: 10.0.50.14 I'm trying to install the app Nextcloud with the address 10.0.50.1, but get: "Error response from daemon: Address already in use". I can however install with the address 10.0.50.2 For whatever reason I get the same error with vlan 51 when using address 10.0.50.17, but not on vlan 52 when using 10.0.50.33. I've been searching through the network of unraid and docker and can't seem to find any trace of the ip address 10.0.50.1. So the question is: How does Unraid lookup used ip addresses? adsnas-diagnostics-20220903-2110.zip Edited September 4, 2022 by Smakodak Forgot to attach logs Quote Link to comment
Recommended Posts
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.