Error response from daemon: Address already in use

[Smakodak]

Hi,

I have numerous vlans all configured like this:
10.0.50.x/28 where x is the second last address in range. The last address in range 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 Nextcloud 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.
Does anyone have an idea of what is causing this behavior and, not less important, how to fix it?

Regards, Anders

 

The full docker command with error:

Command:
[email protected]:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nextcloud' --net='br0.50' --ip='10.0.50.1' -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e HOST_HOSTNAME="ADsNAS" -e HOST_CONTAINERNAME="nextcloud" -e 'TCP_PORT_443'='443' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:443]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nextcloud-logo.png' -v '/mnt/user/nextcloud/':'/data':'rw' -v '/mnt/user/appdata/nextcloud':'/config':'rw' 'lscr.io/linuxserver/nextcloud'

41141042fd5b3386f6b3c298040925ef7e971fbfd1bd4ca7c41bbda179e1b50b
docker: Error response from daemon: Address already in use.

The command failed.

 

adsnas-diagnostics-20220907-0927.zip

[AndrewZ]

@bonienl  Any thoughts you might have here?  I'm assuming that @Smakodak has rebooted already.

[Smakodak]

I did in fact reboot it. It didn't solve it, which in a way is a good thing. Rebooting isn't really a cure, it's a treatment...

[bonienl]

When no explicit gateway address is given for the subnet, then docker will assign the first address as gateway address. This is the conflict you see.

 

Under docker settings you need to set the specific subnet assignment for each VLAN, see example below

 

[Smakodak]

Alright, now it's working. Thank you

 

 

Edited September 16, 2022 by Smakodak
Misread the post that I was answering