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

Autodetection should handle the case where linux-user-chroot is installed but missing kernel features prevent it from working #4

Open
ssssam opened this issue Jun 16, 2015 · 0 comments

Comments

@ssssam
Copy link
Contributor

ssssam commented Jun 16, 2015

The executor_for_platform() function will return the linux_user_chroot backend if the linux-user-chroot binary exists in PATH.

However, depending on kernel configuration, it may not fully work. We found one case where it ran correctly, unless the --unshare-net flag was passed, when it would exit with clone: Invalid argument. On other kernels it won't run at all because it can't create a mount namespace.

Probably the best way to fix this would be to actually run linux-user-chroot during the autodetection, and test whether that works.

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

No branches or pull requests

1 participant