Bug 1096816
Summary: | useradd within EL6 container fails: failure while writing changes to /etc/passwd | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Daniel Walsh <dwalsh> |
Component: | libselinux | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Eduard Benes <ebenes> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.5 | CC: | admiller, dcleal, dwalsh, ebenes, gabor.pihaj, golang-updates, jkeck, jpazdziora, jumanjiman, lvrabec, mattdm, mgoldman, mmalik, petrkuzel, sct, s, vbatts |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libselinux-2.0.94-5.6.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1096123 | Environment: | |
Last Closed: | 2014-10-14 06:41:24 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: | 1096123 | ||
Bug Blocks: |
Description
Daniel Walsh
2014-05-12 13:27:29 UTC
Libselinux needs to check if the /selinux or /sys/fs/selinux is mounted as read/only and then say SELinux is disabled. This would stop SELinux aware applications from attempting to do SELinux actions while in a container. 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1469.html This bug is used as exemplary for The limits of compatibility and supportability with containers <https://www.redhat.com/en/blog/limits-compatibility-and-supportability-containers>. I understand that for the same image and the same hosting kernel, the docker service upgrade impacted behaviour of the container. Despite the docker service upgrade impacted containers it was not seen as a regression in the docker service but it was evaluated as that the upgrade detected a latent bug in the container and preserving a bug-to-bug backward compatibility was not beneficial was it, please? |