Key | Value |
---|---|
FileName | ./usr/bin/mirror-registry |
FileSize | 9912488 |
MD5 | 4720063665860010A9477206D0661254 |
SHA-1 | 071A2AA98AC01CD080D235A0FBC3904AF954C700 |
SHA-256 | D6FEEC12300EAF138D2506E3412122544FA936CF2BDFE51E49C3E48C110FED2E |
SSDEEP | 49152:w5haa+7xf7q5Uvt5TRY0qKLj8e4ZwoZd0g97JQnJgZmS7qoql:wGf7q5Uvt5TvqiIeqweBuF |
TLSH | T1BEA6D6C1A991C34AD52E5A32EBD69FD4F5373A33ACC40A8DE6C5E37C3DB627041A9460 |
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 | 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 |