Key | Value |
---|---|
FileName | ./usr/bin/mirror-registry |
FileSize | 9949456 |
MD5 | 01FAF23767A559DDDB0017428180D850 |
SHA-1 | FFF5CFBFDB481814D3251D9C26839B875720A343 |
SHA-256 | 89646FB4FA60A1C277355B27DB8E0390345A7156A388EA03280CE4C0B3E249D8 |
SSDEEP | 98304:cngnXORyMobr2LLAI07ek71JANnzuWMA+:cngXOEJOLLAI07ek71JANzu5A+ |
TLSH | T10CA62946FC9205EDC5FEE13086A15239B97138E5833037D31F9096A91B66BD46B3E3E8 |
hashlookup:parent-total | 1 |
hashlookup:trust | 55 |
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 |
---|---|
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 |