Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v2] vulnerability scan on container inside a kubernetes cluster failing #1133

Closed
6 tasks
gnmahanth opened this issue May 24, 2023 · 0 comments
Closed
6 tasks
Assignees
Labels
bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration

Comments

@gnmahanth
Copy link
Contributor

Describe the bug
Running a vulnerability scan on container inside a kubernetes cluster is failing

To Reproduce
Steps to reproduce the behavior:

  1. Run vulnerability scan on container on a kubernetes cluster

Expected behavior
Scan should pass

Agent package-scanner logs
INFO[2023-05-24T11:05:38Z] grpc.go:122 SBOMRequest: source:"ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" scan_type:"all" scan_id:"ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288-1684926283" node_type:"container" host_name:"do-mahanth-k8s-pool-fwu5o" container_id:"ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" INFO[2023-05-24T11:05:41Z] syft.go:39 ContainerScan: &{containerId:ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288 tempDir:/tmp/syft-141585100 namespace:default} INFO[2023-05-24T11:05:41Z] autodetect.go:181 connected successfully to endpoint: unix:///run/containerd/containerd.sock INFO[2023-05-24T11:05:41Z] autodetect.go:181 connected successfully to endpoint: unix:///run/containerd/containerd.sock INFO[2023-05-24T11:05:49Z] autodetect.go:218 container runtime detected: containerd ERRO[2023-05-24T11:05:49Z] syft.go:65 errored: container "ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" in namespace "default": not found ERRO[2023-05-24T11:05:49Z] syft.go:167 container "ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" in namespace "default": not found ERRO[2023-05-24T11:05:49Z] grpc.go:194 error in generating sbom: container "ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" in namespace "default": not found INFO[2023-05-24T11:12:09Z] grpc.go:122 SBOMRequest: source:"ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" scan_type:"all" scan_id:"ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288-1684926700" node_type:"container" host_name:"do-mahanth-k8s-pool-fwu5o" container_id:"ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" INFO[2023-05-24T11:12:12Z] syft.go:39 ContainerScan: &{containerId:ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288 tempDir:/tmp/syft-2734634405 namespace:default} INFO[2023-05-24T11:12:12Z] autodetect.go:181 connected successfully to endpoint: unix:///run/containerd/containerd.sock INFO[2023-05-24T11:12:12Z] autodetect.go:181 connected successfully to endpoint: unix:///run/containerd/containerd.sock INFO[2023-05-24T11:12:20Z] autodetect.go:218 container runtime detected: containerd ERRO[2023-05-24T11:12:20Z] syft.go:65 errored: container "ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" in namespace "default": not found ERRO[2023-05-24T11:12:20Z] syft.go:167 container "ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" in namespace "default": not found ERRO[2023-05-24T11:12:20Z] grpc.go:194 error in generating sbom: container "ec854c42a45ca23ecd4a2ba75d35677b5ec2ab264dfbdbe0837ab4116c023288" in namespace "default": not found

Components/Services affected

  • UI/Frontend
  • API/Backend
  • Agent
  • Deployment/YAMLs
  • CI/CD Integration
  • Other (specify)

Additional context
Kubernetes cluster on digital ocean
version: v1.26.3
runtime: containerd://1.6.14

@gnmahanth gnmahanth added bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration labels May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-triage Indicates that issue is not yet triaged and assigned v2 ThreatMapper revamp based on neo4j integration
Projects
None yet
Development

No branches or pull requests

1 participant