returned non-zero after checkpointed

Open
#1,348 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
cli

Research direction

Reproduce with config.json using runc run root in one terminal and runc checkpoint root in another, then inspect the reported exit status (137). The issue names no source file, test, expected status, or completion criterion, so the checkpoint and process-exit paths must be traced before defining a fix and regression test.

Written by the indexing model from the issue text.

Description

process args = "sleep", "6000" in config.json

terminal 1> runc run root
terminal 2> runc checkpoint root
terminal 1> echo $?
terminal 1> 137

Dominant language
Go
Stars
13.5k
Forks
2.3k
Avg merge
2d 8h
Merged PRs (30d)
30

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opencontainers/runc

All issues in opencontainers/runc

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.