Key | Value |
---|---|
FileName | ./usr/share/doc/packages/mirror-registry/README.md |
FileSize | 1225 |
MD5 | 4FA9E59B2B4EB89E1D70211F229CF1D7 |
SHA-1 | F39109A2DFCA2EA25E6A5E355FD5248C45A628CC |
SHA-256 | E3FE9D1421E24FF9C145CF5EFA910F6CF4717E80FA5510091C544E1573B114D9 |
SSDEEP | 24:LuMuXWFtM6OKiaGHFXf/VWXrINz52gd1GIUsJtpqFJBxRO8UrMoFJBN:LuMuT3Ko/VWXENz52gd1GxsJm+dr/N |
TLSH | T18721AD1BDF45B96317D242FD7D7A22B07F2280C181664E52FB3492FC61654DE193F6A0 |
hashlookup:parent-total | 18 |
hashlookup:trust | 100 |
The searched file hash is included in 18 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
MD5 | 9F46264D144CC90B40F899561729A5B7 |
PackageArch | s390x |
PackageDescription | 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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | mirror-registry |
PackageRelease | bp153.1.65 |
PackageVersion | 1.1 |
SHA-1 | 001A578DCC94A066DA7A5C324D1CBD7713034EA6 |
SHA-256 | A3147F92691D81A8DA20CC18073BE1CBD047B6D3CA64920D515043CD9D11109E |
Key | Value |
---|---|
MD5 | 764A65F9D22F70F7044128DD857972CF |
PackageArch | x86_64 |
PackageDescription | 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. |
PackageName | mirror-registry |
PackageRelease | 6.78 |
PackageVersion | 1.1 |
SHA-1 | 1516FB158B82C20166B40F755BB3CA0F9DAA73F0 |
SHA-256 | EF6BA2F62CE2D65656EA6444F60C09B9C10AEAB6892A6F1DC4AA69BE603870C3 |
Key | Value |
---|---|
MD5 | 5D08B307413FB63DFFAE239338EC56F2 |
PackageArch | x86_64 |
PackageDescription | 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. |
PackageName | mirror-registry |
PackageRelease | 6.11 |
PackageVersion | 1.1 |
SHA-1 | 23DA734F5449E344348B9899F02476A4992A54AA |
SHA-256 | EA985C93DFF10AD46AE8E2B9E7CCBE1730417006D24C356534FBAC0C53A01E5A |
Key | Value |
---|---|
MD5 | CB3DAE8C5079963096E437402084D1E0 |
PackageArch | s390x |
PackageDescription | 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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | mirror-registry |
PackageRelease | bp154.1.41 |
PackageVersion | 1.1 |
SHA-1 | 347060C1EA0EEF3AFFB4A64403FA0BF0BBF2E947 |
SHA-256 | 3F816424A2F43740DC2A112ED1B78B8DF27FBA11011958F29E106D3F71365D6F |
Key | Value |
---|---|
MD5 | CF64664B00BE486EF99806A43202F1A5 |
PackageArch | x86_64 |
PackageDescription | 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. |
PackageName | mirror-registry |
PackageRelease | lp151.5.1 |
PackageVersion | 1.1 |
SHA-1 | 3BFD4BAF56A25546A62B4EF63461AC4453105700 |
SHA-256 | EA8FED573893A3DDEC5DE06B0D1B44E71B41BF7FBECAF3F5B4043342220D691E |
Key | Value |
---|---|
MD5 | 3AB399FEB818E0F8ED7B8ED30ADF0CAB |
PackageArch | x86_64 |
PackageDescription | 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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | mirror-registry |
PackageRelease | bp154.1.41 |
PackageVersion | 1.1 |
SHA-1 | 3CE7C9507A64853A33FAB165F0C5DE699DAB1B54 |
SHA-256 | 9E254BC7AC4875341188390FE00A6F6D10EA4B92CA3082E9EC3B39AFD9881BE7 |
Key | Value |
---|---|
MD5 | 04A50FE2961CF9C99E631E97EAD012BD |
PackageArch | s390x |
PackageDescription | 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. |
PackageName | mirror-registry |
PackageRelease | 6.77 |
PackageVersion | 1.1 |
SHA-1 | 6097D3F5466E7A46D7132638B5986E420D6CF43B |
SHA-256 | 882129EECE4BD97C81C7DEC26B4309E23599616AD0EE954F423991E227B7E48B |
Key | Value |
---|---|
MD5 | B56DF8D1BBBD3889FBDBFCB7031E5FAE |
PackageArch | x86_64 |
PackageDescription | 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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | mirror-registry |
PackageRelease | bp155.1.7 |
PackageVersion | 1.3 |
SHA-1 | 7DDD82222CE139DF7C1E1FEC843A6C0ED32335D8 |
SHA-256 | 4EAE80D62D172B22F1A7564D657B9D977EBEB8B07E8C092970E9A9C8EF70DABA |
Key | Value |
---|---|
MD5 | C1E4589FDC1DE49B3CECBEB6634B826B |
PackageArch | x86_64 |
PackageDescription | 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. |
PackageName | mirror-registry |
PackageRelease | lp152.6.5 |
PackageVersion | 1.1 |
SHA-1 | A4E5FD037438778A0BBFD6797ED7CA7FA1665198 |
SHA-256 | 59F955129016329FF0139E2C0BB952C3A730DE905E2E5047C99E8BFD0B7AD76B |
Key | Value |
---|---|
MD5 | 252F7B28058AED2A671BDD78DF5AED20 |
PackageArch | s390x |
PackageDescription | 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. |
PackageMaintainer | https://bugs.opensuse.org |
PackageName | mirror-registry |
PackageRelease | bp156.1.14 |
PackageVersion | 1.4 |
SHA-1 | AB933B1CD0D48D5B23DF6BF7EB00C13838797736 |
SHA-256 | FAD1D558F8AC103D7F02C9DADFE6A7AE30825E5A312943C2C2CA7FA2DDB5997E |