To reproduce add any container and reboot the host system.
set container name busybox allow-host-networks set container name busybox image 'busybox'
vyos@r1-roll:~$ reboot now Connection to 192.168.122.11 closed by remote host. Connection to 192.168.122.11 closed. sever@sever:~$ ping 192.168.122.11 PING 192.168.122.11 (192.168.122.11) 56(84) bytes of data. 64 bytes from 192.168.122.11: icmp_seq=1 ttl=64 time=0.208 ms 64 bytes from 192.168.122.11: icmp_seq=2 ttl=64 time=0.225 ms 64 bytes from 192.168.122.11: icmp_seq=3 ttl=64 time=0.245 ms 64 bytes from 192.168.122.11: icmp_seq=4 ttl=64 time=0.215 ms 64 bytes from 192.168.122.11: icmp_seq=5 ttl=64 time=0.170 ms 64 bytes from 192.168.122.11: icmp_seq=6 ttl=64 time=0.210 ms ... ... 64 bytes from 192.168.122.11: icmp_seq=77 ttl=64 time=0.154 ms 64 bytes from 192.168.122.11: icmp_seq=78 ttl=64 time=0.324 ms 64 bytes from 192.168.122.11: icmp_seq=79 ttl=64 time=0.179 ms 64 bytes from 192.168.122.11: icmp_seq=80 ttl=64 time=0.193 ms 64 bytes from 192.168.122.11: icmp_seq=81 ttl=64 time=0.207 ms 64 bytes from 192.168.122.11: icmp_seq=82 ttl=64 time=0.149 ms From 192.168.122.1 icmp_seq=93 Destination Host Unreachable From 192.168.122.1 icmp_seq=94 Destination Host Unreachable From 192.168.122.1 icmp_seq=95 Destination Host Unreachable From 192.168.122.1 icmp_seq=96 Destination Host Unreachable
After about one and a half minutes, the system will reboot
A possible reason then containers created from VyOS CLI can't correctly handle SIGTERM signal (or just ignore it) to process "pid 1"
After sending SIGTERM it waits 1.5 min and then send SIGKILL, only after this the system is going into reboot.