Infinite loop on !killall docker-init

[rohitner]

Describe the current behavior
Runtime is killed on executing !killall docker-init and colab starts another runtime leading to infinite allocation loop

Describe the expected behavior
Runtime should be guarded against !killall docker-init as it does against !reboot and !shutdown as follows

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

What web browser you are using
Brave

[EvanWiederspan]

Tracking internally as b/396487972 - can you say more about why you want to run this command though?

[rohitner]

Please note that there is no particular use case for above mentioned command similar to non use case of !reboot and !shutdown. It is meant to highlight a scenario where collab runtime allocator may allocate resources sub-optimally.