Open sophokles73 opened 1 year ago
I have killed the QEMU process and started up leda again. The changes I had made to the manifest files have been picked up and now I am also able to shutdown leda properly.
I have witnessed the same or a similar problem on Raspberry Pi: systemctl restart container-management
would hang indefinitely. In that case, the device was under heavy load and running on a possibly broken SD-Card (CRC errors when trying to back it up).
We were using a Kuksa.VAL Seat Service example container reconfigured with physical CAN-Bus access, host networking and in privileged mode. It's unclear what the root cause was, but we could not properly shut down the system any more. The Kanto container-management socket interface was not coming up any more (hence, kantui and kanto-cm were not able to connect to the container-management daemon).
Also stopping the service did not properly work either.
The file /run/container-management/netns/default
was locked, but unsure whether this is related.
Describe the bug I have run the latest 0.0.6 image for x86_64 and am not able to restart (nor stop) the container-management service in order to pick up some changes I made in some deployment manifest files.
To Reproduce Steps to reproduce the behaviour:
systemctl restart container-management
Expected behaviour container-management service stops and restarts after a few seconds
Leda Version (please complete the following information):