Key | Value |
---|---|
FileName | ./usr/bin/mirror-registry |
FileSize | 12773872 |
MD5 | E2EE941E3CC37EC3628C4BF4E0B7AE8E |
SHA-1 | 7437763B47B6000527D8C6FC403FEE639754C2E4 |
SHA-256 | 617C22EE2D10538ACD7AFD15F2B513ECE7FF13C7DC86DA1D68AB57B556920DE3 |
SSDEEP | 196608:v+HTc2UIbHf7d7KPSrAGXXiyQRU8YerKBW:v+gWD0PVYerK |
TLSH | T1B9D64C56FCC640DDC6BEE17485959731BA713856833437834FA08A9E935ABE4AB3E3C0 |
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 | 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 |