Skip to content

【Bug】crictl exec failed  #8860

@ZP-AlwaysWin

Description

@ZP-AlwaysWin

Description

error message

[root@node ~]# crictl exec -ti dbe69c0cbc610 bash
FATA[0000] execing command in container failed: error sending request: Post http://127.0.0.1:34185/exec/NjxYongN:
dial tcp 127.0.0.1:42491: connect: connection refused

The containerd process is running normally, but the listening port exits
image
image

Start the code for containerd. If port listening fails, an error will be reported and exit. If there is no error or exit, it indicates successful startup。why the listening port exits?

image

Steps to reproduce the issue

Describe the results you received and expected

Why does the port exit

What version of containerd are you using?

v1.7.1

Any other relevant information

No response

Show configuration if it is related to CRI plugin.

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions