Bug 1627900
Summary: | [RFE] skopeo Image on Red Hat Container Catalog | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Richard Foyle <rfoyle> |
Component: | skopeo-container | Assignee: | Jindrich Novy <jnovy> |
Status: | CLOSED ERRATA | QA Contact: | Yuhui Jiang <yujiang> |
Severity: | medium | Docs Contact: | Gabriela Nečasová <gnecasov> |
Priority: | medium | ||
Version: | 8.0 | CC: | ajia, aos-bugs, ddarrah, dornelas, dwalsh, gnecasov, hgomes, jnovy, jokerman, kanderso, leiwang, lfriedma, lmanasko, lmiksik, mmccomas, mpatel, pasik, pweil, smccarty, tsweeney, weshen, xtian, yujiang |
Target Milestone: | rc | Keywords: | FutureFeature, TechPreview |
Target Release: | 8.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
.`skopeo` container image is now available
The `registry.redhat.io/rhel8/skopeo` container image is a containerized implementation of the `skopeo` package. The `skopeo` tool is a command-line utility that performs various operations on container images and image repositories. This container image allows you to inspect container images in a registry, to remove a container image from a registry, and to copy container images from one unauthenticated container registry to another. To pull the `registry.redhat.io/rhel8/skopeo` container image, you need an active Red Hat Enterprise Linux subscription.
|
Story Points: | --- |
Clone Of: | 1627899 | Environment: | |
Last Closed: | 2020-04-28 23:10:57 UTC | Type: | Feature Request |
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: | |||
Bug Blocks: | 1186913, 1734579 |
Comment 2
Daniel Walsh
2019-03-08 20:29:58 UTC
*** Bug 1794419 has been marked as a duplicate of this bug. *** 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://access.redhat.com/errata/RHEA-2020:1956 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |