Jan 13 12:08:56 Hal-1 kernel: ip_tables: © 2000-2006 Netfilter Core Team

The System log shows after Docker startup:

 

Jan 13 12:08:56 Hal-1 avahi-daemon[10165]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.42.1.

Jan 13 12:08:56 Hal-1 avahi-daemon[10165]: New relevant interface docker0.IPv4 for mDNS.

Jan 13 12:08:56 Hal-1 avahi-daemon[10165]: Registering new address record for 172.17.42.1 on docker0.IPv4.

Jan 13 12:08:57 Hal-1 kernel: device veth56f3 entered promiscuous mode

Jan 13 12:08:57 Hal-1 kernel: docker0: port 1(veth56f3) entered forwarding state

Jan 13 12:08:57 Hal-1 kernel: docker0: port 1(veth56f3) entered forwarding state

Jan 13 12:08:57 Hal-1 avahi-daemon[10165]: Withdrawing workstation service for veth7f7c.

Jan 13 12:08:58 Hal-1 kernel: docker0: port 1(veth56f3) entered disabled state

Jan 13 12:08:58 Hal-1 kernel: docker0: port 1(veth56f3) entered forwarding state

Jan 13 12:08:58 Hal-1 kernel: docker0: port 1(veth56f3) entered forwarding state

 

 

When I start a Docker image of a DNLA server it is bound to 172.17.42.x so it doesn't appear on my network. How can it be made to show up on my network?

 

I'm sorry I can't give a copy and paste solution right now but read this: https://docs.docker.com/articles/networking/