Error: unsupported MediaType: "application/vnd.docker.distribution.manifest.v1+prettyjws" #609
-
am getting below error in startboard-operator. GKE cluster version: v1.19.9-gke.1400
Could you please help me to resolved this issue? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I think you have all the details in the error log.
Starboard integrates with Trivy static vulnerability scanner, which does not support (ancient) manifest Just to confirm, the same behaviour is reproducible with Trivy run directly so there's nothing we can do about it in Starboard plugin for Trivy: $ trivy image quay.io/coreos/kube-rbac-proxy:v0.4.1
2021-05-28T09:22:15.419+0200 INFO Need to update DB
2021-05-28T09:22:15.419+0200 INFO Downloading DB...
21.52 MiB / 21.52 MiB [-----------------------------------------------------------------------------------------------------] 100.00% 47.22 MiB p/s 1s
2021-05-28T09:22:17.718+0200 FATAL scan error: unable to initialize a scanner: unable to initialize a docker scanner: 3 errors occurred:
* unable to inspect the image (quay.io/coreos/kube-rbac-proxy:v0.4.1): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
* unable to initialize Podman client: no podman socket found: stat podman/podman.sock: no such file or directory
* unsupported MediaType: "application/vnd.docker.distribution.manifest.v1+prettyjws", see https://github.com/google/go-containerregistry/issues/377 |
Beta Was this translation helpful? Give feedback.
I think you have all the details in the error log.
Starboard integrates with Trivy static vulnerability scanner, which does not support (ancient) manifest
application/vnd.docker.distribution.manifest.v1+prettyjws
. Trivy relies on https://github.com/google/go-containerregistry/ module and the error log also points out to the GitHub issue, where you can find the whole discussion about v1+prettyjws manifest on google/go-containerregistry#377Just to confirm, the same behaviour is reproducible with Trivy run directly so there's nothing we can do …