Docker Port Mapping broken?

[Slarti123]

Hi all,

 

I've had a lot of dockers running succesfully.

 

When I installed a new one (Traccar) I experienced an "Execution Error- bad parameter".

 

I tried to install that as custom Br0 with own (free) IP. I did realize that in the overview the port mapping shows 0.0.0.0 instead of 192.XXX.

Anyway, I had the same error with every other "Network Type". I decided to put it aside and look at it later.

 

Another Docker was running smoothly. But I wanted a clean restart (TVHeadend).

 

It was set up as custom Br0 with 192(...)15 and worked.

 

I did remove it through the GUI and re-installed it as before (without any error). I did also use the same Network parameters.

 

Now, I see the same: I cannot  run the docker ("Server Error" instead of "bad parameter"), but all mappings show 0.0.0.0 instead of the desired 192....15.

 

Any idea where to start?
(not even sure, if the two occurences are dependent).

 

Thanks!

 

 

Edited July 3, 2022 by Slarti123

[Squid]

The docker run command will show exactly why it's coming up like that.

[Slarti123]

Thanks for the fast reply.

My docker run shows no errors and is as follows:

 

 

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='tvheadend_neu' --net='br0' --ip='192.168.178.15' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'RUN_OPTS'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -v '/mnt/user/Media/Video/Aufnahmen/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend':'/config':'rw' --device='/dev/dri' --device='/dev/dvb' 'lscr.io/linuxserver/tvheadend'
1ee57545183880d2da1786e6a8993b32db491fbc1920a8273ef94afa6759b5d2

The command finished successfully!

 

What I did just see in the log is that:

 

Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state
Jul 3 16:29:11 Server kernel: device veth78599bd entered promiscuous mode
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered blocking state
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered forwarding state
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state
Jul 3 16:29:11 Server kernel: device veth78599bd left promiscuous mode
Jul 3 16:29:11 Server kernel: docker0: port 5(veth78599bd) entered disabled state

 

Edited July 3, 2022 by Slarti123

[Squid]

Copy and paste this command into the terminal.  It should return an error

docker run --name='tvheadend_neu' --net='br0' --ip='192.168.178.15' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_9981'='9981' -e 'TCP_PORT_9982'='9982' -e 'RUN_OPTS'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -v '/mnt/user/Media/Video/Aufnahmen/':'/recordings':'rw' -v '/mnt/user/appdata/tvheadend':'/config':'rw' --device='/dev/dri' --device='/dev/dvb' 'lscr.io/linuxserver/tvheadend'

 

You're in a weird edge case because the container isn't running, so the procedure to get the error message doesn't work because it doesn't try to start the container.

[Slarti123]

Thank you!

 

I get that one:

docker: Error response from daemon: Conflict. The container name "/tvheadend_neu" is already in use by container
"1ee57545183880d2da1786e6a8993b32db491fbc1920a8273ef94afa6759b5d2".
You have to remove (or rename) that container to be able to reuse that name.

 

[Slarti123]

Thank you!

Solved:

 

TL;DR
had to delete everything (image, container) including the "appdata" folder and re-install without error messages.
 

Edited July 4, 2022 by Slarti123