CODEWITHSUNDEEP
dockerdocker-machinedocker-registryjfrog-container-registrydocker-daemon
Jaraws
Jaraws

Reputation: 691

Getting docker error, daemon is missing signature key on docker pull

I have been trying to pull a docker image; which has been pushed successfully to the private jfrog repository using the same terminal and in same session. There comes no issues while pushing the image, however on doing a pull it is getting failed with the following region.

[xxxx@xxxx~]$ sudo docker pull  docker-repo/xxxx-xxxx-xxx/xx/tomcat-xx:latest
Error response from daemon: missing signature key

If anyone can help what could be reason for this? The difference I can see wrt to the image I pushed through this terminal and the images which are already present in jfrog repo is that manifest has cetain properties associated with them. However, there are no properties present in jfrog repo wrt to image I pushed from this terminal.

Following are the details for reference:

$ sudo docker version
Client: Docker Engine - Community
 Version:           19.03.5
 API version:       1.40
 Go version:        go1.12.12
 Git commit:        633a0ea
 Built:             Wed Nov 13 07:25:41 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.5
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.12
  Git commit:       633a0ea
  Built:            Wed Nov 13 07:24:18 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.10
  GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
 runc:
  Version:          1.0.0-rc8+dev
  GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Is there anything I am missing at configuration end. Kindly help. Thanks.

Upvotes: 5

Views: 38612

Answers (3)

Narayan
Narayan

Reputation: 125

In my case I found it was just an old image tag that was not in the registry anymore.

Upvotes: 0

dimir
dimir

Reputation: 793

The error message suggests that it's something wrong on the client side. In my case it was my docker version being too old. I upgraded it and the error was gone.

In fact, my OS version was too old so I had to upgrade it (Debian 9 -> 10), the newer version of OS had the newer version of docker.

Upvotes: 8

O. Trouvé
O. Trouvé

Reputation: 81

I had the same problem with JFrog Artifactory. For me, it helped to give annotate permissions to the user pushing the image, as suggested here.

Upvotes: 1

Related Questions