Locked interaction with containers after rebooting

[andrsj]

I used the KM version: v0.11.14 on two different machines with Windows

Got a problem - after the rebooting the both of Linux system on different machines I can't reach into container logs, inspecting, pausing, etc. All buttons are inactive into Container Manager and Node manager also always tries to load info, but unsuccessfully.

But they are working (htop on screen):

Second machine:

One of them - WSL:

wsl --version
WSL version: 1.2.0.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.19045.2846

Windows:

systeminfo
Host Name:                 DESKTOP-RBHGRM5
OS Name:                   Майкрософт Windows 10 Pro
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free

Second in VM (from VirtualBox):

Windows:

systeminfo
Host Name:                 ADERKACH-NB
OS Name:                   Microsoft Windows 10 Enterprise
OS Version:                10.0.19045 N/A Build 19045
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free