Bug 1875289
| Summary: | podman run with --rm errors out/segfaults in container-tools-2.0-8.3.0 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Michele Baldessari <michele> | |
| Component: | podman | Assignee: | Jindrich Novy <jnovy> | |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.3 | CC: | ajia, bbaude, dciabrin, ddarrah, dornelas, dwalsh, imcleod, jligon, jnovy, jwboyer, lmiccini, lsm5, mheon, ypu | |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
|
| Target Release: | 8.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | podman-1.6.4-21.el8 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1882267 (view as bug list) | Environment: | ||
| Last Closed: | 2020-11-04 03:45:29 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1882267 | |||
|
Description
Michele Baldessari
2020-09-03 08:28:04 UTC
Ouch. It looks like Podman 1.6 in the 2.0 stream was rebuilt with a newer Golang. Unfortunately, the newer Go runtime made the decision that Signal 23 is reserved exclusively for its use (for preempting threads) and sends several of them per second. In older Podman versions, our signal-proxying logic will unconditionally forward these into the container, and can (potentially) trigger error messages like the one you saw as part of a race around container stop. We addressed the race and stopped forwarding the signal in newer Podman, but the 1.6 series never got the patch because it was only built with the older Go compiler. Upstream patches to resolve: https://github.com/containers/podman/commit/868ee6db7057a63e09dc67b7448a6f13efcdddd3 (Closes the race around container exit and sig-proxy) https://github.com/containers/podman/commit/e6fba1e44898304a0c5560aaecdee53beda1034f (Ignores Signal 23 so we don't spam containers with excess signals) I can reproduce this bug on podman-1.6.4-14.module+el8.3.0+7660+b7198318 w/ runc-1.0.0-64.rc10.module+el8.3.0+7994+3dff63cb. [root@ibm-x3650m4-01-vm-02 ~]# podman run -it --net=host --rm --user=root ecbc6f53bba0 sh -c 'touch /tmp/foo && ls /tmp' foo ks-script-7n1migha ERRO[0000] Error forwarding signal 23 to container 2895faceb0870a9c1be9d694d17d3073362038943d713a1dfecbf9ebb8ff3752: container has already been removed And verify it on podman-1.6.4-21.module+el8.3.0+7994+3dff63cb.x86_64 w/ runc-1.0.0-64.rc10.module+el8.3.0+7994+3dff63cb [root@ibm-x3650m4-01-vm-02 ~]# podman run -it --net=host --rm --user=root ecbc6f53bba0 sh -c 'touch /tmp/foo && ls /tmp' foo ks-script-7n1migha [root@ibm-x3650m4-01-vm-02 ~]# echo $? 0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (container-tools:2.0 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4770 |