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

fix mount crio sock #14

Closed
wants to merge 1 commit into from
Closed

fix mount crio sock #14

wants to merge 1 commit into from

Conversation

anngdinh
Copy link

Node agent need mount crio sock

@def
Copy link
Member

def commented Dec 21, 2023

It's not necessary to mount this because the agent can access the host filesystem

@anngdinh
Copy link
Author

I got this error if not mount

image

@def
Copy link
Member

def commented Dec 21, 2023

Please show the beginning of the log

@anngdinh
Copy link
Author

image

@def
Copy link
Member

def commented Dec 21, 2023

As you can see in the log, the agent tried to access the cri-o socket through: /proc/1/root/var/run/crio/crio.sock but encountered the no such file or directory error. This issue may arise if /var/run/crio/crio.sock or /var/run/crio is a symlink. Could you please check this?

@anngdinh
Copy link
Author

No. It's not a symlink, it's a sock file. But i don't understand why node agent can read the file if I don't mount it.

@def
Copy link
Member

def commented Dec 21, 2023

The agent runs in the host PID namespace and has access to the proc filesystem. It can reach the host mount namespace through /proc/1/root/...

@anngdinh
Copy link
Author

I see /proc/1/root -> /. I don't really catch it.
image

@def
Copy link
Member

def commented Dec 21, 2023

To understand this, please read the section explaining /proc/pid/root in this documentation

@def def closed this Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants