Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Container remains Stopped after container-management service restart #191

Closed
stoyan-zoubev opened this issue Aug 22, 2023 · 0 comments · Fixed by #214
Closed

Container remains Stopped after container-management service restart #191

stoyan-zoubev opened this issue Aug 22, 2023 · 0 comments · Fixed by #214
Assignees
@k-gostev
Labels
task Single unit of work
Milestone
M5

Comments

@stoyan-zoubev
Copy link
Contributor

I have a container that wants to communitate with Kanto CM over gRPC. That's why my container is created with moun point like
--mp="/run/container-management/container-management.sock:/run/container-management/container-management.sock".

It is all fine, container is created and started successfully through the kanto-cm CLI.

However, the problem occurs when Kanto container-management service is restarted. Then my container remains stopped and not starting automatically.

The following message is seen in the kanto-cm log file.
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 = 1eb42aec-8bb9-4da7-833e-fa3030a245a5 \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 mounting \"/run/container-management/container-management.sock\" to rootfs at \"/run/container-management/container-management.sock\": stat /run/container-management/container-management.sock: no such file or directory: unknown "

I guess the loading and restarting of previously available containers is performed before the starting of Kanto-CM gPRC server, that's why the container-management.sock file does not yet exist and mounting fails.

But could it make a container restart attempt later? What about container's restart policy, it seems to be ignored in this case...

A workaround is to use a mount point only to --mp="/run/container-management:/run/container-management".
@k-gostev k-gostev added this to the M5 milestone Sep 4, 2023
@k-gostev k-gostev added the task Single unit of work label Sep 12, 2023
@k-gostev k-gostev moved this to Todo in Eclipse Kanto Sep 12, 2023
@k-gostev k-gostev self-assigned this Nov 13, 2023
@k-gostev k-gostev moved this from Todo to In Progress (max 10) in Eclipse Kanto Nov 21, 2023
@k-gostev k-gostev mentioned this issue Nov 21, 2023
Merged
@k-gostev k-gostev linked a pull request Nov 21, 2023 that will close this issue
Rearrange daemon startup sequence #214
Merged
@k-gostev k-gostev moved this from In Progress (max 10) to Ready for Review (max 3) in Eclipse Kanto Nov 22, 2023
@dimitar-dimitrow dimitar-dimitrow moved this from Ready for Review (max 3) to In Review (max 3) in Eclipse Kanto Nov 22, 2023
dimitar-dimitrow pushed a commit that referenced this issue Nov 22, 2023
@k-gostev
Rearrange daemon startup sequence (#214)
0dabb8c 
[#191] Container remains Stopped after container-management service restart 

* Rearrange daemon startup sequence
* Add dev branch to the workflow

Signed-off-by: Kristiyan Gostev <[email protected]>
@dimitar-dimitrow dimitar-dimitrow moved this from In Review (max 3) to Done in Eclipse Kanto Nov 22, 2023
k-gostev added a commit that referenced this issue Apr 30, 2024
@k-gostev
Rearrange daemon startup sequence (#214)
a8f764d 
[#191] Container remains Stopped after container-management service restart 

* Rearrange daemon startup sequence
* Add dev branch to the workflow

Signed-off-by: Kristiyan Gostev <[email protected]>
dimitar-dimitrow added a commit that referenced this issue May 10, 2024
@k-gostev @daniel-milchev
@stoyan-zoubev @dimitar-dimitrow
Merge dev-m5 into main (#235)
a951f1c 
[#234] Merge `dev-m5` branch into `main`
* [#51] Improve containerd client unit tests (#203)
* [#201] Optimized, deterministic intermediate desired state feedback messages (#204)
* [#208] Add file flag to the CLI create command (#209)
* [#191] Container remains Stopped after container-management service restart (#214)
* [#210] Remove command should accept more than one container ID (#212)
* [#196] Starting of constantly restarting container fails (#216)
* [#67] Implement signed images verification (#215)
* [#91] Provide unit tests covering signed images verification (#220)
* [#213] Add quiet flag, to the list command. (#221)
* [#217] CLI Remove command improvements (#224)

---------

Signed-off-by: Daniel Milchev [email protected]
Signed-off-by: Stoyan Zoubev <[email protected]>
Signed-off-by: Kristiyan Gostev <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Co-authored-by: Daniel Milchev <[email protected]>
Co-authored-by: Stoyan Zoubev <[email protected]>
Co-authored-by: Dimitar Dimitrov <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@k-gostev k-gostev

Labels
task Single unit of work
Projects
Eclipse Kanto
Status: Done
Milestone
M5
Development

Successfully merging a pull request may close this issue.

Rearrange daemon startup sequence bosch-io/container-management
3 participants
@stoyan-zoubev @dimitar-dimitrow @k-gostev