Result for E6DDFEE11C1A36AF8AC011D1CE57F7D1A381123D

Query result

Key Value
FileName./usr/bin/mirror-registry
FileSize9760368
MD59A28A8E482EB7639D195AA02255A9A6C
SHA-1E6DDFEE11C1A36AF8AC011D1CE57F7D1A381123D
SHA-256EA7CA8FED969DB27D2013932654362C103348271CD7D630209F44180C0A2CAA6
SSDEEP98304:P33PCoO6trdc8FJ6w8J9IptcryRSsxH4/dCgjhthnN42fCFY0E:yBovFwwqx9XJCSN
TLSHT146A629D3E85540ECC1BDC2308A658A72BA61785A8F30E3C35B65A7B71792BD45F7A3C0
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
MD5764A65F9D22F70F7044128DD857972CF
PackageArchx86_64
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.
PackageNamemirror-registry
PackageRelease6.78
PackageVersion1.1
SHA-11516FB158B82C20166B40F755BB3CA0F9DAA73F0
SHA-256EF6BA2F62CE2D65656EA6444F60C09B9C10AEAB6892A6F1DC4AA69BE603870C3