This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
When creating a Bodhi update request, use the bodhi submission link noted
in the next comment(s). This will include the bug IDs of this tracking
bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
epel-7 tracking bug for docker-io: see blocks bug list for full details of the security issue(s).
[bug automatically created by: add-tracking-bugs]
Use the following update submission link to create the Bodhi request for
this issue as it contains the top-level parent bug(s) as well as this
tracking bug. This will ensure that all associated bugs get updated when
new packages are pushed to stable.
IMPORTANT: ensure that the "Close bugs when update is stable" option
Bodhi update submission link:
docker-io is already in Fed 20. Recommended fix is to simply pull from EPEL.
The epel7 build has been removed since docker is available in RHEL 7 extras. Perhaps we need to make more noise to make people aware in case they're still using the epel7 build(?)
The epel 7 build is still here, so this bug cannot be "closed".
People who use docker from epel currently open a way to get root to any user, so I reopen this bug until this is fixed.
I'm not sure what the right answer is... maybe update the EPEL package with a stub with a readme telling people where to get the RHEL7 extras? (Including, I assume, the CentOS equivalent?)
1) I assume that there's a CentOS equivalent (or they just pull it into the main repo instead of shoving it in a different repo like RHEL does for supportability reasons...)
2) I'm not 100% sure what the "right way" to remove a package from EPEL that has been subsumed into RHEL proper is. Obviously the standard package retirement, but since the RHEL package in question here is:
a) in a different repo that is disabled by default, and
b) of a different name entirely
presents something of an issue since the RHEL package is not going to be NEVRA newer than the EPEL package, nor does the RHEL package provide what the EPEL package does:
$ rpm -q --provides docker
docker = 0.11.1-22.el7
docker(x86-64) = 0.11.1-22.el7
lxc-docker = 0.11.1
I think that we might need to get the RHEL maintainers to provide docker-io in the docker package in order to facilitate the upgrade path from the EPEL to the RHEL version, though the version that is in EPEL right now is newer than the RHEL version that's out right now anyhow.
Is the EPEL package wishing to continue to be updated? If so, the same fix that went into the RHEL package (which is simply disabling socket activation, there's some other systemd work that needs to happen in order to get it back) needs to go into the EPEL version.
Given the support level of docker in RHEL, I don't see why the EPEL version would/should be maintained.
(In reply to Jon Stanley from comment #6)
> Is the EPEL package wishing to continue to be updated? If so, the same fix
> that went into the RHEL package (which is simply disabling socket
> activation, there's some other systemd work that needs to happen in order to
> get it back) needs to go into the EPEL version.
Docker should be removed from EPEL7.
docker-io build has been removed from epel7 https://dl.fedoraproject.org/pub/epel/beta/7/x86_64/ (nothing in there)
epel7 branch has the install steps for default docker package https://pkgs.fedoraproject.org/cgit/docker-io.git/tree/dead.package?h=epel7