Key | Value |
---|---|
FileName | ./usr/bin/mirror-registry |
FileSize | 12773872 |
MD5 | 35D8DCD24893089B76D8997CD1B0A61C |
SHA-1 | 679B9A9E9720EE77BE61DF076C758052E795569E |
SHA-256 | BE66D68B0D5FED6ABA281DE759D124B852BE1BE63AD1FC1B45F1AC7C8621AF8A |
SSDEEP | 98304:T4Rkv3Lk7EnAPkBk93S9aWHWN1I1Z5E14a1sSYNX:z3Lk7EcCk93S9aWWNqZ5Eiao |
TLSH | T170D63A06FC8604DEC1BEE2B085969731B9713899837837934FA1969D9356BE4A73F3C0 |
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 | C1E4589FDC1DE49B3CECBEB6634B826B |
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 | lp152.6.5 |
PackageVersion | 1.1 |
SHA-1 | A4E5FD037438778A0BBFD6797ED7CA7FA1665198 |
SHA-256 | 59F955129016329FF0139E2C0BB952C3A730DE905E2E5047C99E8BFD0B7AD76B |