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

Skip to content

ExecSync failed for VM runtime #4224

@liubin

Description

@liubin

For vm runtimes, the Pid and InitPid status is not set for container state, that will lead ExecSyncto fail.

Logs(new lines added for reading):

Sep 28 03:11:34 master kubelet[2399]: E0928 03:11:34.685127   
 2399 remote_runtime.go:351] ExecSync 
dd11b99bb03a6aa5a6b5ffcd0f4a8aa2ba180b3a84d7b9d16175e4ff543193a0 
'cat /tmp/healthy' from runtime service failed: 
rpc error: code = NotFound desc = container is not created or running:
 checking if PID of dd11b99bb03a6aa5a6b5ffcd0f4a8aa2ba180b3a84d7b9d16175e4ff543193a0 
is running failed: container PID not initialized

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