Networking: no route to host

[Strum355]

Ingress and outgress networking doesnt work when spinning up vms from example, see screenshot.
I can attach to VM and do anything that doesnt involve

Host:

> ip addr show cni0                                                                                                                                                                                                                         Thu 05 Sep 2019 18:19:44 IST
51: cni0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 16:94:03:be:10:25 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global cni0
       valid_lft forever preferred_lft forever
    inet6 fe80::1494:3ff:febe:1025/64 scope link 
       valid_lft forever preferred_lft forever

VM:

root@localhost:~# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 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: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether ea:9a:88:b7:ad:bf brd ff:ff:ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 8a:ef:19:a1:97:55 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.6/16 brd 172.18.255.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::88ef:19ff:fea1:9755/64 scope link 
       valid_lft forever preferred_lft forever

[chanwit]

Thank you for reporting @Strum355
There's some fixes going to to the master in #421 . Not sure if it's gonna solve your issue.

$ sudo bin/ignite ps
[sudo] password for chanwit: 
VM ID                   IMAGE                           KERNEL                                  SIZE    CPUS    MEMORY          CREATED STATUS  IPS             PORTS   NAME
17b100016889f1d3        weaveworks/ignite-ubuntu:latest weaveworks/ignite-kernel:4.19.47        4.0 GB  1       512.0 MB        20m ago Up 20m  172.18.0.4              white-wave
$ ping 172.18.0.4
PING 172.18.0.4 (172.18.0.4) 56(84) bytes of data.
64 bytes from 172.18.0.4: icmp_seq=1 ttl=64 time=0.200 ms
64 bytes from 172.18.0.4: icmp_seq=2 ttl=64 time=0.473 ms
^C
--- 172.18.0.4 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1028ms
rtt min/avg/max/mdev = 0.200/0.336/0.473/0.137 ms

[chanwit]

#421 will be dropped in favor of #427

[Strum355]

Issue has been resolved 👍 Theres still an issue where ignite (or whoever responsible) picks a subnet that conflicts with a docker subnet however, but i think theres an open issue for that already

[chanwit]

yes, we have a plan to change subnet in 0.7.0.

However it's a breaking change, so 0.6.1 still uses the same subnet with documented as it might collide with a Docker bridge network.