Starting of constantly restarting container fails

[dimitar-dimitrow]

When a constantly restarting container update is received from the Update Manager, the Container's Update Agent, tries to start the container. However, there seems to be a concurrency problem, between the UA and the auto restart mechanism. The update activity finishes with status INCOMPLETE and the following error is logged:

time="2023-08-31T09:28:17.50888366Z" level=error msg="[container-management][ctrd_client.go:255][pkg:github][func:com/eclipse-kanto/container-management/containerm/ctr] error creating task for container ID = cd0be8fb-e533-4cce-bbc4-f0db9d0775d8 \n\t Error: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time=\"2023-08-31T09:28:17Z\" level=fatal msg=\"no sandbox present for cd0be8fb-e533-4cce-bbc4-f0db9d0775d8\": unknown " time="2023-08-31T09:28:17.525847659Z" level=error msg="[container-management][update_operation.go:546][pkg:github][func:com/eclipse-kanto/container-management/containerm/updateagent] could not start container [hello-world] \n\t Error: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time=\"2023-08-31T09:28:17Z\" level=fatal msg=\"no sandbox present for cd0be8fb-e533-4cce-bbc4-f0db9d0775d8\": unknown "