Parents (Total: 16)

The searched file hash is included in 16 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	DECADF6A5D0552718AAF5184631102AB
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	102.git7f2769b.el7.centos
PackageVersion	1.13.1
SHA-1	026B077910A49262EC508C108517FA1F7B4BFFB1
SHA-256	C68AAB1E255E6B3A15794FF0D74131BF1F5EC0B729012A7F27C977A2D256EE9E

Key	Value
MD5	58B0A37F32C10D2810FFB2CD73E45570
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	208.git7d71120.el7_9
PackageVersion	1.13.1
SHA-1	054999804C93AE5F3A4A1025050ABFA79FEABAE2
SHA-256	7EBCE393C8C09724257B1DEC782332DEA86747906D0FD1C73028DEEC11A5B25D

Key	Value
MD5	2DFD3D03E33B1FC9461A31A79969E1F6
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-latest-v1.10-migrator
PackageRelease	58.git87f2fab.el7.centos
PackageVersion	1.13.1
SHA-1	143AEAADAA500E87C031C8AFEAC3DED013ED2A42
SHA-256	3EF14036989CDE2E96A7739AB55E700FF8F6ED63F2A7424283EAC353680BCF35

Key	Value
MD5	1F02049A5328622AC8A3251DA14DB58A
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	93.gitb2f74b2.el7
PackageVersion	1.13.1
SHA-1	1D0AAEA0D7C78C6C0E7E8F075ABFBF2777F829E9
SHA-256	10E136F6CD553CCEC08F659E2DF4A295AC3A17FF9D83DA79481B06A5778EBF2A

Key	Value
MD5	782FC34F5310A944FDADD19A79018E47
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	206.git7d71120.el7_9
PackageVersion	1.13.1
SHA-1	892F234EC0FB8CD0BD0C8F4EC99A4AA9673D13A8
SHA-256	E3890CF6AE0E63C6F6B0CE8BF3DF2A5BC34BD184CCDF0A272869EC73C827D660

Key	Value
MD5	0F3425F57C1AEC5778709C12B9C40943
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	205.git7d71120.el7.centos
PackageVersion	1.13.1
SHA-1	907E7D1942C0808536BEFD07C5C6C6169F3C9346
SHA-256	EB27675E07677F0006093AD9901BE8116AF56155AE6CDAEAA14A4E5BEA782495

Key	Value
MD5	783DDE705E918031F7D7E7EC1A1F48FF
PackageArch	x86_64
PackageDescription	Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere. Docker containers can encapsulate any payload, and will run consistently on and between virtually any server. The same container that a developer builds and tests on a laptop will run at scale, in production*, on VMs, bare-metal servers, OpenStack clusters, public instances, or combinations of the above.
PackageMaintainer	CBS <cbs@centos.org>
PackageName	docker
PackageRelease	59.1.el7
PackageVersion	1.10.3
SHA-1	920F1FE6FA3232614E2BD90E7006A669BA20EB37
SHA-256	2143A6983C9CD9BE66E8A290B13A358FFC517641A20B8B23B3B7D0705AA45CB8

Key	Value
MD5	79C7DEF4B685F9C5DB07BF26CC2CB5A8
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	162.git64e9980.el7.centos
PackageVersion	1.13.1
SHA-1	9940796219351B0B782809B636719795DB05B8B9
SHA-256	2A79882B3BC48CA2B4768B7DC5F0658F29705A0C18AC12BB7FB8B4777C528F9E

Key	Value
MD5	09EE3F23963B735E585A04096246C651
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	203.git0be3e21.el7.centos
PackageVersion	1.13.1
SHA-1	9BD03EE27B7B5AEDF884ED6E7657E5F70CB454D5
SHA-256	FC15F2B62E0FD263BB2714B744919439E96FE992B25E0C56D34B6BD1F393F581

Key	Value
MD5	F8B7FCD04EC111298C5C4AE960A36A60
PackageArch	x86_64
PackageDescription	Starting from v1.10 docker uses content addressable IDs for the images and layers instead of using generated ones. This tool calculates SHA256 checksums for docker layer content, so that they don't need to be recalculated when the daemon starts for the first time. The migration usually runs on daemon startup but it can be quite slow(usually 100-200MB/s) and daemon will not be able to accept requests during that time. You can run this tool instead while the old daemon is still running and skip checksum calculation on startup.
PackageMaintainer	CentOS BuildSystem <http://bugs.centos.org>
PackageName	docker-v1.10-migrator
PackageRelease	109.gitcccb291.el7.centos
PackageVersion	1.13.1
SHA-1	AB317B48A97023A6A743D983FC9D726827431900
SHA-256	92DD5313691C3F8DCCB2A3C725DDCFE8AA6DE3EF79708D5F926A0C31F5A91D48