How to fix Docker "missing signature key" client error
During 'docker pull' request, you may encounter the "missing signature key" error from the Docker client.
According to our previous experience, this error happens when one or more properties of the manifest.json file are missing or may be wrong.
Since the issue can be caused due to replication wasn't finished correctly, the simplest way to fix it is to re-push or re-replicate the image.
If this is not possible, you may manually add the missing properties of the manifest.json.
The relevant properties for the manifest.json are as follows:
The values should be set as follow:
The docker.manifest value is the name of the tag/docker-folder in Artifactory, for example:
The docker.manifest.digest value is using the following format: "sha256:<sha256 value of the manifest.json>" – this can be taken from the general tab of the manifest.json 'Checksums' section:
The docker.manifest.type value is the manifest type which in most cases is "application/vnd.docker.distribution.manifest.v2+json".
The docker.repoName value is the name of the image/folder (which represents the image in Artifactory), for example:
The sha256 is also the SHA-256 of the manifest.json file.