Just reproduced manually:[root@vz8 ~]# vzctl start 1000 Starting Container ... ... [root@vz8 ~]# vzctl enter 1000 entered into CT 1000 CT-1000 /# pidof rpcbind CT-1000 /# rpcinfo > /dev/null 2>&1 CT-1000 /# pidof rpcbind 678 CT-1000 /#Thanks for info. I'm asking because if it's a setup bug it should not be hidden by workaround but reported. I suppose normal Centos8 VM works.
I's say this is starting service on demand and this is exactly what socket activation is designed for.
