Example 1: unable to ping IP address of xe-0/0/0 and xe-0/0/1 interfaces

[kcao3]

@mwiget I have a question for you. I am currently following your example 1. At this point,I am able to run the vmx Docker container on a Docker host machine. From the CLI of my vmx Docker container,
I am able to ping the IP address of the fxp0 interface but NOT the other two IP addresses of the xe-0/0/0 and xe-0/0/1 interfaces.
Also, if when shell into my vmx container from the Docker host, I am not able to ping any of these IP addresses. Is that expected? If not, do you know how to resolve this problem? Thanks in advance for your help. Below are the actual ping results:

root@vmx> ping 172.17.0.22
PING 172.17.0.22 (172.17.0.22): 56 data bytes
64 bytes from 172.17.0.22: icmp_seq=0 ttl=64 time=0.167 ms
64 bytes from 172.17.0.22: icmp_seq=1 ttl=64 time=0.122 ms
64 bytes from 172.17.0.22: icmp_seq=2 ttl=64 time=0.071 ms
^C
--- 172.17.0.22 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.071/0.120/0.167/0.039 ms

root@vmx> ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
^C
--- 10.0.0.1 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

root@vmx> ping 1.1.2.1
PING 1.1.2.1 (1.1.2.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
^C
--- 1.1.2.1 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

[root@floyd7 vmxdocker]# docker exec -it vmx1 /bin/sh

ping 172.17.0.22

PING 172.17.0.22 (172.17.0.22) 56(84) bytes of data.
^C
--- 172.17.0.22 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

[mwiget]

Is the PFE up when you tried the ping command? You can check with 'show chassis fpc'. Also, once the FPC is online, you will see the interfaces xe-0/0/0 and xe-0/0/1 via 'show interface xe-0/0/*'. It usually takes a few minutes for the PFE to become online.