Bug 1811779
| Summary: | RFE: skopeo sync command | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Jaroslav Spanko <jspanko> |
| Component: | skopeo | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | ddarrah, dornelas, gnecasov, jnovy, kanderso, mitr, tsweeney, vrothber, ypu, yujiang |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | skopeo-0.1.41 | Doc Type: | Enhancement |
| Doc Text: |
.Containers registries now support the `skopeo sync` command
With this enhancement, users can use `skopeo sync` command to synchronize container registries and local registries.
The `skopeo sync` command is useful to synchronize a local container registry mirror, and to populate registries running inside of air-gapped environments.
The `skopeo sync` command requires both source (`--src`) and destination (`--dst`) transports to be specified separately.
Available source and destination transports are `docker` (repository hosted on a container registry) and `dir` ( directory in a local directory path).
The source transports also include `yaml` (local YAML file path).
For information on the usage of `skopeo sync`, see the `skopeo-sync` man page.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-07-21 15:31:55 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, 1793607 | ||
|
Description
Jaroslav Spanko
2020-03-09 18:20:16 UTC
In case a link to the upstream PR is helpful: https://github.com/containers/skopeo/pull/524 and we also need to be sure to get: https://github.com/containers/skopeo/pull/798. These are both contained in this release: https://github.com/containers/skopeo/releases/tag/v0.1.41 Jindrich, I'm going to assign this to you and set it as POST as I think this is a matter of preparing the release at this point. It looks like if you use the yaml src format you can specify *only* the tags you want to sync. I would suggest that there also be a mechanism to filter out specific tags (with a glob would be nice). My main concern is filtering out RH's Source container images. These can be very large (multiple GBs in some instances), and, just like most customers do not download/install src rpms, I don't think they will want or expect these source containers when they sync. Sure, I've just opened https://github.com/containers/skopeo/issues/852 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/RHSA-2020:3053 |