Prisma Cloud Compute: Defender Log Error: cri.go:663 Failed to find image for container & Container
2602
Created On 04/30/23 22:01 PM - Last Modified 10/24/24 16:32 PM
Question
- Why does the Defender log show the following error message? (just an example)
ERRO 2023-02-07T00:34:29.189 cri.go:663 Failed to find image for container &Container{Id:1aa3985696bd6f0bb0ed46a2039357c617f6db1c9da235de36c0dacb33c002f2,PodSandboxId:aec497eff04f34e987ff8dc3c3a09c7e53fc045fa95aa543107d89b095872ffa,Metadata:&ContainerMetadata{Name:registry-server,Attempt:0,},Image:&ImageSpec{Image:icr.io/cpopen/ibm-operator-catalog@sha256:245d4b5d3d9c9e4e19e0f1e925738fd536e278e0b29aae60ff13d455b6537484,Annotations:map[string]string{},},ImageRef:icr.io/cpopen/ibm-operator-catalog@sha256:245d4b5d3d9c9e4e19e0f1e925738fd536e278e0b29aae60ff13d455b6537484,State:CONTAINER_RUNNING,CreatedAt:1675700198144670451,Labels:map[string]string{io.kubernetes.container.name: registry-server,io.kubernetes.pod.name: opencloud-operators-4mq6h,io.kubernetes.pod.namespace: pro-bkapi0-001,io.kubernetes.pod.uid: 2622a367-7666-4f6a-b282-f4b078655e48,},Annotations:map[string]string{io.kubernetes.container.hash: 833d4d55,io.kubernetes.container.ports: [{"name":"grpc","containerPort":50051,"protocol":"TCP"}],io.kubernetes.container.restartCount: 0,io.kubernetes.container.terminationMessagePath: /dev/termination-log,io.kubernetes.container.terminationMessagePolicy: FallbackToLogsOnError,io.kubernetes.pod.terminationGracePeriod: 30,},}
- Is it safe to ignore the above error message? Does it impact the scanning of the containers?
Environment
- Prisma Cloud Compute - SaaS
- Container Defender (v22.06.197 in this example)
- Openshift
Answer
- The concerned error message shows when the container Defender scans the running container and finds that the image reference (ImageRef) is missing. Example of a image reference is as follows:
ImageRef:icr.io/cpopen/ibm-operator-catalog@sha256:245d4b5d3d9c9e4e19e0f1e925738fd536e278e0b29aae60ff13d455b6537484
- Yes, it is safe to ignore the error message as it shall not impact the Defender's ability to scan the containers. The scans shall continue to operate as expected/desired