Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[1.19] invalid infra container using crictl with vm type runtime (kata) #4264

@fgiudici

Description

@fgiudici

Description

CRI-O 1.19 and cri-tools v1.19.0 installed.
Kata containers shimv2 installed and configured as default runtime for CRI-O.
Basic example from cri-tools fails.

Steps to reproduce the issue:
Start CRI-O 1.19 with containerd-shim-kata-v2 as the default runtime an run the cri-tools example:

# crictl runp pod-config.json
175d4a12122cdd3ee51e0e74b8d111f67245aa3ba0373694eba188668707f544
]# crictl create 175d4a12122cdd3ee51e0e74b8d111f67245aa3ba0373694eba188668707f544 container-config.json pod-config.json
FATA[0010] creating container: rpc error: code = Unknown desc = PID namespace requested, but sandbox infra container invalid

Additional information you deem important (e.g. issue happens only occasionally):
When the pod is created, the infra container has the state InitPid not initialized (set to 0).
This triggers the error on container creation.

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