Bug 1670223 - Update runc to latest version
Summary: Update runc to latest version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: runc
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-28 23:55 UTC by Andrew Pietsch
Modified: 2019-02-21 01:38 UTC (History)
7 users (show)

Fixed In Version: runc-1.0.0-68.dev.git6635b4f.fc29 runc-1.0.0-68.dev.git6635b4f.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-15 02:38:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Andrew Pietsch 2019-01-28 23:55:08 UTC 
Description of problem:

The current version of runc doesn't include https://github.com/opencontainers/runc/pull/1933.  Without it options like --tcp-established can't be configured which in turn causes `docker checkpoint` to fail in all but the simplest cases.


Version-Release number of selected component (if applicable):

$ runc --version
runc version 1.0.0-rc6+dev


How reproducible:

Every time.

Steps to Reproduce:
1. Start a container that opens TCP connections.
2. run `docker checkpoint` on the container.
3.

Actual results:

Error response from daemon: Cannot checkpoint container 38c5d6de19c6: runc did not terminate sucessfully: criu failed: type NOTIFY errno 0 path= /var/run/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/38c5d6de19c6bfde5bf6053796b75bc2adbaafcfa154cce6d46284ab62058760/criu-dump.log: unknown

Error log includes message to specify --tcp-established option.

Expected results:
Checkpoint to be created.

Additional info:
More discussion at: https://github.com/checkpoint-restore/criu/issues/599#issuecomment-457084690
Comment 1 Fedora Update System 2019-02-12 16:08:38 UTC 
runc-1.0.0-68.dev.git6635b4f.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-3f19f13ecd
Comment 2 Fedora Update System 2019-02-12 16:24:47 UTC 
runc-1.0.0-68.dev.git6635b4f.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-963ea958f9
Comment 3 Fedora Update System 2019-02-12 20:26:24 UTC 
runc-1.0.0-68.dev.git6635b4f.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3f19f13ecd
Comment 4 Fedora Update System 2019-02-13 06:00:58 UTC 
runc-1.0.0-68.dev.git6635b4f.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-963ea958f9
Comment 5 Fedora Update System 2019-02-15 02:38:38 UTC 
runc-1.0.0-68.dev.git6635b4f.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
Comment 6 Fedora Update System 2019-02-21 01:38:52 UTC 
runc-1.0.0-68.dev.git6635b4f.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.