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

Possibility of LXD container support #2108

Open
DullJZ opened this issue Jun 1, 2024 · 2 comments
Open

Possibility of LXD container support #2108

DullJZ opened this issue Jun 1, 2024 · 2 comments

Comments

@DullJZ
Copy link

DullJZ commented Jun 1, 2024

After a period of time of container study, I finally turned to LXC/LXD.

Using LXD to create a debian container, I found sysdig failed to collect data from it. Also sysdig -c lscontainers shows no result.

The lxd dir is /var/snap/lxd/common, if snap was used to install LXD.

Now that both Docker and LXC/LXD share the kernel with the host, I think it possible for sysdig to moniter and record on LXC/LXD.

@DullJZ
Copy link
Author

DullJZ commented Jun 2, 2024

Found that sysdig container.id!=host can successfully record the events in lxd container.

However, sysdig -p "%container.id" container.id!=host output only \n. In other words, sysdig cannot identify lxd container's ID.

As I tried Falco, it can identify my lxd container name:

12:35:06.232167470: Warning Sensitive file opened for reading by non-trusted program (file=/etc/shadow gparent=lxd ggparent=lxd gggparent=daemon.start evt_type=openat user=<NA> user_uid=1000000 user_loginuid=-1 process=cat proc_exepath=/usr/bin/cat parent=bash command=cat /etc/shadow terminal=34817 container_id=my-test container_name=my-test)

I hope sysdig can identify it as Falco does.

Copy link

github-actions bot commented Oct 1, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Oct 1, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2024
@therealbobo therealbobo removed the stale label Oct 9, 2024
@therealbobo therealbobo reopened this Oct 9, 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

No branches or pull requests

2 participants