Bug 1330366
Summary: | [extras-rhel-7.2.4] docker-latest should Requires: docker-common | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Lokesh Mandvekar <lsm5> |
Component: | docker-latest | Assignee: | Lokesh Mandvekar <lsm5> |
Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
Severity: | low | Docs Contact: | Yoana Ruseva <yruseva> |
Priority: | unspecified | ||
Version: | 7.2 | CC: | ajia, atomic-bugs, bbreard, dwalsh, jhonce, lsm5, mmcgrath, pruan, santiago, sghosh |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | docker-latest-1.10.3-13.el7 | Doc Type: | Enhancement |
Doc Text: |
Feature: /usr/bin/docker script calls /usr/bin/docker-latest by default if 'docker' is not installed
Reason: Users of docker-latest (or docker) only want to
use the 'docker' command without needing to constantly check which version of docker daemon is actually being run
Result: /usr/bin/docker and /etc/sysconfig/docker provided by the docker-common package allow the admin to configure which docker client binary gets called. /usr/bin/docker will call /usr/bin/docker-latest by default when 'docker' is not installed. If 'docker' is installed, /usr/bin/docker will call /usr/bin/docker-current by default, unless DOCKERBINARY is set to /usr/bin/docker-latest in /etc/sysconfig/docker
|
Story Points: | --- |
Clone Of: | 1328219 | Environment: | |
Last Closed: | 2016-05-12 14:56:06 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: | 1328219 | ||
Bug Blocks: | 1303656, 1305185 |
Description
Lokesh Mandvekar
2016-04-26 03:35:04 UTC
What is the default for docker-common? What happens if I only install docker-latest and don't install docker? This kind of breaks the rpm checking, since it would be better to see that docker is using docker-latest rather then docker-common. I don't think this should block us from moving ahead, but we should open a bugzilla on this. Dan, when only docker-latest is installed, /usr/bin/docker will call /usr/bin/docker-latest by default. lsm5 @ rhel7 : ~ $ rpm -q docker docker-latest package docker is not installed docker-latest-1.10.3-22.el7.x86_64 lsm5 @ rhel7 : ~ $ sudo docker version Client: Version: 1.10.3 API version: 1.22 Package version: docker-common-1.9.1-40.el7.x86_64 Go version: go1.4.2 Git commit: 86bbf84/1.10.3 Built: OS/Arch: linux/amd64 Server: Version: 1.10.3 API version: 1.22 Package version: docker-common-1.9.1-40.el7.x86_64 Go version: go1.4.2 Git commit: 86bbf84/1.10.3 Built: OS/Arch: linux/amd64 lsm5 @ rhel7 : ~ $ Excellent. 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. https://rhn.redhat.com/errata/RHEA-2016-1057.html |