Skip to content

containerd-socket-tracer logs "null" for certain workloads #61

@chrishenzie

Description

@chrishenzie

This is anecdotal evidence but I've heard for some users the containerd-socket-tracer workload occasionally logs null. I have reason to believe one example this happens for is the wiz-sensor container, which is known to call the CRI v1alpha2 API.

Until I can get access to Wiz API keys to install their chart and test this myself, if anyone is able to test this and open a PR that is much appreciated.

Steps to repro

  1. Install containerd-socket-tracer
  2. Install wiz-sensor
  3. Restart wiz-sensor Pod
  4. Observe logs of containerd-socket-tracer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions