Result for C2A348DD454AD2595EFCFEE86373554E716CB49D

Query result

Key Value
FileName./usr/bin/mirror-registry
FileSize11383736
MD5BF42D670983CC80371E4435F68109D15
SHA-1C2A348DD454AD2595EFCFEE86373554E716CB49D
SHA-25624A1F5C6AAB0D0EE528B9A03DC2B60E4CEEFE96E0447FD0CB68F3AE8FFC4FDC9
SSDEEP49152:OmfjmQw3mbrnHHHsEh0T1RMdjk7QMkjspP2KGghIInH+kKu:O8mQw3mbzHHHbiTHSjYQnsRTnd
TLSHT1AEB62BE1E890C34AD6BD1A30EBD69FD8D63B36335CD41A4DC6D5E33D38A12B494B9920
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD59F46264D144CC90B40F899561729A5B7
PackageArchs390x
PackageDescriptionmirror-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.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp153.1.65
PackageVersion1.1
SHA-1001A578DCC94A066DA7A5C324D1CBD7713034EA6
SHA-256A3147F92691D81A8DA20CC18073BE1CBD047B6D3CA64920D515043CD9D11109E