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

Install sysdig or some other tool to help with Singularity troubleshooting #191

Open
martbhell opened this issue Mar 31, 2017 · 2 comments

Comments

@martbhell
Copy link
Contributor

This role looks useful to install sysdig: https://github.com/valentinogagliardi/sysdig

@martbhell
Copy link
Contributor Author

Tried out this role on a compute node in io.
Worked without any issues.
Running role worked - but it defaults to setting things to latest which I like to avoid.
Sent a PR https://github.com/valentinogagliardi/sysdig/pull/6

@martbhell
Copy link
Contributor Author

PR is merged and this could not be added.

@martbhell martbhell added the ready label Apr 5, 2017
martbhell added a commit that referenced this issue Apr 3, 2018
This provides some useful tools like:
 - csysdig (a top for containers)
 - falco (a service that audits suspicious activity inside containers)

For now only in compute.yml (so not for ansible-pull).

Use CSCfi/ansible-falco fork. The old sysdig role we looked at in #191
 has disappeared

Have tested that "journalctl -xefu falco" writes things to the journal
when "event_generator -a all" is run from within this container:

singularity run docker://sysdig/falco-event-generator
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant