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.

Sign up for GitHub

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

Jump to bottom

Rationale for explicitly calling unshare(2) in child_fn after clone(2) #4

Open

lujiajing1126 opened this issue Dec 31, 2020 · 0 comments

lujiajing1126 commented Dec 31, 2020

According to the man page of unshare(2), https://man7.org/linux/man-pages/man2/unshare.2.html

CLONE_NEWNS: This flag has the same effect as the clone(2) CLONE_NEWNS flag.

May be a trivial question, but forgive me since I am new to this area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment