Description of problem:
The container-selinux package does not Obsolete the docker-selinux which can lead to a situation especially when upgrading that both packages are installed which in turn causes error messages about duplicate label definitions.
Since container-selinux aims to replace docker-selinux it should Obsolete docker-selinux on RPM level.
Version-Release number of selected component (if applicable):
We should also do docker-engine-selinux.
Apologies I missed this. I guess at the moment this issue can be taken care of by manually removing docker-selinux, correct?
We can file this as a known issue until the next update.
(In reply to Lokesh Mandvekar from comment #3)
> Apologies I missed this. I guess at the moment this issue can be taken care
> of by manually removing docker-selinux, correct?
Correct, rpm -e docker-selinux or yum remove-n docker-selinux will do the trick. (Note the usage of remove-n instead of remove, if only container-selinux is present then yum remove docker-selinux would currently remove container-selinux.)
On an Atomic Host, the only way to do this would be
# ostree admin unlock
# rpm -e docker-selinux
Is that right? Correct me if I'm wrong.
This issue shouldn't affect Atomic Host, since every base commit is like a fresh install.
Does it affect RHEL users?
(In reply to Yoana Ruseva from comment #7)
> Does it affect RHEL users?
This a bug report filed against RHEL 7.
This has been documented as a known issue here:
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.