Bug 1396531 - Skopeo and atomic do not depend on skopeo-containers
Summary: Skopeo and atomic do not depend on skopeo-containers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: skopeo
Version: 7.3
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: Martin Jenner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-18 15:03 UTC by David Darrah/Red Hat QE
Modified: 2020-09-21 08:07 UTC (History)
3 users (show)

Fixed In Version: skopeo-1:0.1.17-0.7.git1f655f3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-06 17:42:44 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2866 0 normal SHIPPED_LIVE skopeo bug fix and enhancement update 2016-12-06 22:40:33 UTC

Comment 1 Micah Abbott 2016-11-18 15:20:26 UTC
In case you don't follow that pastebin link, this is what happens after installing atomic/skopeo:

Installed:
  atomic.x86_64 1:1.13.8-1.el7                                                                                                                                                                                     

Dependency Installed:
  docker.x86_64 0:1.10.3-57.el7              docker-common.x86_64 0:1.10.3-57.el7  docker-rhel-push-plugin.x86_64 0:1.10.3-57.el7  docker-selinux.x86_64 0:1.10.3-57.el7  python-docker-py.noarch 0:1.9.0-1.el7 
  skopeo.x86_64 1:0.1.17-0.5.git1f655f3.el7 

Complete!

# atomic pull busybox
Image busybox is being pulled to docker ...
The docker daemon does not appear to be running.
# systemctl start docker
# atomic pull busybox
Image busybox is being pulled to docker ...
Trying docker.io/library/busybox:latest
Pulling docker.io/library/busybox:latest ...
FATA[0000] Error loading trust policy: open /etc/containers/policy.json: no such file or directory 

# atomic pull registry.access.redhat.com/rhel7
Image registry.access.redhat.com/rhel7 is being pulled to docker ...
Pulling registry.access.redhat.com/rhel7:latest ...
FATA[0000] Error loading trust policy: open /etc/containers/policy.json: no such file or directory 

# docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE


This breaks 'atomic pull', so setting blocker flag

Comment 3 Micah Abbott 2016-11-18 15:28:02 UTC
I don't see a rhel-7.3-z flag, so setting rhel-7.4 + blocker because of rules

Comment 5 David Darrah/Red Hat QE 2016-11-18 20:43:53 UTC
Verified against skopeo-0.1.17-0.6.git1f655f3.el7.x86_64

Comment 13 errata-xmlrpc 2016-12-06 17:42:44 UTC
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/RHBA-2016-2866.html


Note You need to log in before you can comment on or make changes to this bug.