search

sammonsjl / docker-mythtv

0 stars 4 forks source link

mythtv sammonsjl mythtv-30-fixes docker bridged IP4 bug #6

Open RacerXXX opened 4 years ago

RacerXXX commented 4 years ago

Over the past two days I tested mythtv-30-fixes each time no ip4 for mythbackend

First with tested Synology and Docker Then tested OpenmediaVault 5- Debian 10 Buster with Docker , Portainer. Each time when you create the mythackend container it appears is no ip information

When I login with putty and check the ip here is the output

root@OMV5:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group defaul                                                                                                        t qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp2s0f4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default                                                                                                         qlen 1000
    link/ether 00:07:43:15:36:30 brd ff:ff:ff:ff:ff:ff
3: enp2s0f4d1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP grou                                                                                                        p default qlen 1000
    link/ether 00:07:43:15:36:38 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.6/24 brd 192.168.1.255 scope global enp2s0f4d1
       valid_lft forever preferred_lft forever
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP gr                                                                                                        oup default
    link/ether 02:42:49:9f:50:d2 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:49ff:fe9f:50d2/64 scope link
       valid_lft forever preferred_lft forever
10: veth5d7713b@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue ma                                                                                                        ster docker0 state UP group default
    link/ether 82:d9:60:be:15:ca brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::80d9:60ff:febe:15ca/64 scope link
       valid_lft forever preferred_lft forever
14: vethd9e8d3b@if13: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue m                                                                                                        aster docker0 state UP group default
    link/ether 16:1d:27:9a:c7:9b brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::141d:27ff:fe9a:c79b/64 scope link
       valid_lft forever preferred_lft forever
root@OMV5:~#

Here is the code

docker run -d \
    --name=mythbackend \
    -v /volume1/docker/appdata/mythtv/config:/home/mythtv \
    -v /volume1/docker/appdata/mythtv/data:/var/lib/mysql \
    -v /volume1/docker/appdata/mythtv/media:/var/lib/mythtv \
    --hostname=mythbackend --net=host \
    sammonsjl/mythtv:30-fixes

One strange thing is the container for mythtv-30-fixes has the correct ip4 address

bridge | 172.17.0.3 | 172.17.0.1 | 02:42:ac:11:00:03

but the one for the mythbackend container is blank

This page references the ip4 docker bridged bug

https://github.com/moby/moby/issues/38942

nospam2000 commented 4 years ago

You use --net=host in your docker run command. This means the container will not be assigned to a docker network and not get an own ip address, it uses the ip address of the host.