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

Make sure entrypoint runs for docker pod. #226

Merged
merged 1 commit into from
Mar 21, 2017
Merged

Make sure entrypoint runs for docker pod. #226

merged 1 commit into from
Mar 21, 2017

Conversation

mstemm
Copy link
Contributor

@mstemm mstemm commented Mar 21, 2017

If a daemonset specifies a command, this overrides the entrypoint. In
falco's case, the entrypoint handles the details of loading the kernel
driver, so specifying a command accidently prevents the driver from
being loaded.

This happens to work if you had a previously loaded sysdig_probe driver
lying around.

The fix is to specify args instead. In this case, the driver will be
loaded via the entrypoint.

This fixes #225.

If a daemonset specifies a command, this overrides the entrypoint. In
falco's case, the entrypoint handles the details of loading the kernel
driver, so specifying a command accidently prevents the driver from
being loaded.

This happens to work if you had a previously loaded sysdig_probe driver
lying around.

The fix is to specify args instead. In this case, the driver will be
loaded via the entrypoint.

This fixes #225.
@mstemm mstemm merged commit f72182d into dev Mar 21, 2017
@mstemm mstemm deleted the fix-k8s-daemonset branch March 21, 2017 21:45
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.

Running as kubernetes daemonset failing
1 participant