Example 2: Launch 2 vMXs instances in 2 separate containers and connect them via a virtual bridge

[kcao3]

Following your instructions from this example, I was able to launch the two vMX instances in two separate containers.

The following screenshot shows the output when I executed the command show interface and the command show route from one of these vMX instance:

From the CLI of one vMX instance , I was able to ping the IP address of the fxp0.0 interface of the other vMX instance, and vice versa. However, the IP address of the ge-0/0/0 interface is still NOT REACHABLE via ping. Do you know the root cause of this problem and how to fix it?

Also, considering this vMX command: set interface ge-0/0/0.0 family inet address 10.10.10.2/24
Do you know if the interface ge-0/0/0.0 for an vMX instance is supposed to map to a physical NIC (such as eth1) of the Docker Host machine where the vMX container is running (similar to the sample vMX startup configuration shown on page 34 of this link: https://www.juniper.net/techpubs/en_US/vmx15.1/information-products/pathway-pages/getting-started/getting-started.pdf)?

[mwiget]

The PFE doesn't seem to be online yet, hence the lack of ge-0/0/0 and ge-0/0/1 interface in the container. Do a 'show chassis fpc' and see if it is reported as online with numbers greater than 0 for load etc:

--- JUNOS 15.1F4.15 built 2015-12-23 20:22:39 UTC
mwiget@lwaftr1> show chassis fpc
                     Temp  CPU Utilization (%)   CPU Utilization (%)  Memory    Utilization (%)
Slot State            (C)  Total  Interrupt      1min   5min   15min  DRAM (MB) Heap     Buffer
  0  Online           Testing   3         0        2      2      2      1         6          0

You can switch to screen session #1 in tmux via Ctrl-B 1, then you can see what happens on the PFE. Scroll back to see if there are any core dumps by chance.
BTW its important you run this on a bare metal container host, not within a VM.