Zeroconf fails when docker is restarted

sometimes to update my Home Assistant (not Hass.io) I need to do a rm of the docker image and then restart but this leaves ther zeroconf in a non working state for some time. I am guessing this in the mdns cache not quite sure how long it lives for.

2018-09-20 11:14:04 ERROR (MainThread) [homeassistant.setup] Error during setup of component zeroconf
Traceback (most recent call last):
File “/usr/src/app/homeassistant/setup.py”, line 148, in _async_setup_component
component.setup, hass, processed_config) # type: ignore
File “/usr/local/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/app/homeassistant/components/zeroconf.py”, line 55, in setup
zeroconf.register_service(info)
File “/usr/local/lib/python3.6/site-packages/zeroconf.py”, line 1836, in register_service
self.check_service(info, allow_name_change)
File “/usr/local/lib/python3.6/site-packages/zeroconf.py”, line 1952, in check_service
raise NonUniqueNameException
zeroconf.NonUniqueNameException

Hi @vajonam I also found the issue you posted on github, but there I can’t reply. Have you found a way to fix this? I’m hitting the exact same issue.
Running this on the host:

sudo service avahi-daemon restart

does temporary fix this for me, but doing this manually is not fixing it as I would hope.