RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1811779 - RFE: skopeo sync command
Summary: RFE: skopeo sync command
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: skopeo
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913 1793607
TreeView+ depends on / blocked
 
Reported: 2020-03-09 18:20 UTC by Jaroslav Spanko
Modified: 2023-09-07 22:17 UTC (History)
10 users (show)

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.
Clone Of:
Environment:
Last Closed: 2020-07-21 15:31:55 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers skopeo issues 852 0 None open Add filter mechanism to skopeo sync 2021-02-18 20:25:28 UTC
Github containers skopeo pull 524 0 None closed Introduce the sync command 2021-02-18 20:25:29 UTC
Github containers skopeo pull 798 0 None closed add specific authfile options to copy (and sync) command. 2021-02-18 20:25:25 UTC
Red Hat Product Errata RHSA-2020:3053 0 None None None 2020-07-21 15:32:38 UTC

Description Jaroslav Spanko 2020-03-09 18:20:16 UTC
Description of problem:
The skopeo sync command can sync images between a SOURCE and a
destination.


Version-Release number of selected component (if applicable):
skopeo-0.1.40

Actual results:
The skopeo sync command does not exist in RHEL, only on upstream

Expected results:
Implementation of the skopeo sync command

Additional info:
This already exists in upstream
https://github.com/containers/skopeo/commit/9c402f3799493ea5bc01fff6033e1dcebc620d89

Comment 1 Tom Sweeney 2020-03-09 21:48:45 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.

Comment 2 Derrick Ornelas 2020-03-13 18:13:22 UTC
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.

Comment 4 Derrick Ornelas 2020-03-16 17:18:45 UTC
Sure, I've just opened https://github.com/containers/skopeo/issues/852

Comment 19 errata-xmlrpc 2020-07-21 15:31:55 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://access.redhat.com/errata/RHSA-2020:3053


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