How to Install and Uninstall mirror-registry Package on openSuSE Tumbleweed
Last updated: November 23,2024
1. Install "mirror-registry" package
Please follow the instructions below to install mirror-registry on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
mirror-registry
Copied
2. Uninstall "mirror-registry" package
Please follow the instructions below to uninstall mirror-registry on openSuSE Tumbleweed:
$
sudo zypper remove
mirror-registry
Copied
3. Information about the mirror-registry package on openSuSE Tumbleweed
Information for package mirror-registry:
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : mirror-registry
Version : 1.4-1.6
Arch : x86_64
Vendor : openSUSE
Installed Size : 8.3 MiB
Installed : No
Status : not installed
Source package : mirror-registry-1.4-1.6.src
Upstream URL : https://github.com/thkukuk/mirror-registry
Summary : Tool helping to mirror a registry to a private one
Description :
mirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
----------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : mirror-registry
Version : 1.4-1.6
Arch : x86_64
Vendor : openSUSE
Installed Size : 8.3 MiB
Installed : No
Status : not installed
Source package : mirror-registry-1.4-1.6.src
Upstream URL : https://github.com/thkukuk/mirror-registry
Summary : Tool helping to mirror a registry to a private one
Description :
mirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.