Bug 1370628

Summary:	Package dependencies on docker conflict with upstream docker-engine
Product:	[Fedora] Fedora	Reporter:	David O. <root>
Component:	docker	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	adimania, admiller, amurdaca, dwalsh, ichavero, jcajka, jchaloup, lsm5, marianne, miminar, nalin, riek, root, vbatts
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-01 11:29:36 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:

Description David O. 2016-08-26 20:19:18 UTC

Many packages - including kubernetes and atomic (cli) - require the docker package. If someone wants to install the latest upstream package from Docker Inc it will conflict with Fedora's or CentOS's package and that someone won't be able to install anything that depends on docker.

I realize that this is a more complex situation than it seems. But I suggest things that don't need our specific version of docker should only require /usr/bin/docker. If that's not an option then having packages for the latest releases in testing would be great.

Comment 1 Lokesh Mandvekar 2016-08-26 20:41:01 UTC

Hmm, maybe upstream docker-engine could just add a "Provides: docker = %{version}-%{release}

I guess once that's done, you could simply install kubernetes / atomic on top of this upstream rpm.

IIRC, we shouldn't be setting dependencies on individual files but on the entire package.

Comment 2 David O. 2016-08-26 21:36:30 UTC

That sounds like the best solution. I added the related upstream issue.

Comment 3 Jan Chaloupka 2016-08-31 12:35:11 UTC

Assuming all repositories providing "docker" up to one will be disabled. If not, the most recent NVR always wins which can lead to unexpected behaviour. Like installing docker-1.11 instead of expected docker-1.10.

Comment 4 Daniel Walsh 2016-09-01 11:29:36 UTC

We should not worry about people installing random packages on to the distro, the same complaints would happen if a user installed a random upstream glibc.  The distro should not be coding against upstream.  Upstream has to handle this problem.

I don't see this as a Fedora docker bug.