We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
This issue comes from the analysis in: falcosecurity/falco#2897 . Currently, the gVisor engine crashes if a non-hex container ID is used.
How to reproduce it
Example:
# create a container bundle mkdir redis mkdir redis/rootfs docker pull redis docker create --name tempredis redis docker export tempredis | tar -C redis/rootfs -xf - docker rm tempredis cd ./redis/ runc spec cd .. # run a runsc sandbox with a non-hex id sudo runsc -platform=systrap -file-access=shared -host-uds=open -overlay2=none -directfs -dcache=0 --cpu-num-from-quota --pod-init-config=/etc/docker/runsc_falco_config.json -debug-log=/tmp/runsc/ -debug -strace run -bundle redis/ my_container_id
Meanwhile, run Falco (or any libs client) with gVisor integration enabled.
Expected behaviour
Falco should not crash.
Screenshots
Environment
libs 0.14.0
Additional context
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
LucaGuerra
Successfully merging a pull request may close this issue.
Describe the bug
This issue comes from the analysis in: falcosecurity/falco#2897 . Currently, the gVisor engine crashes if a non-hex container ID is used.
How to reproduce it
Example:
Meanwhile, run Falco (or any libs client) with gVisor integration enabled.
Expected behaviour
Falco should not crash.
Screenshots
Environment
libs 0.14.0
Additional context
The text was updated successfully, but these errors were encountered: