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.

Sign up for GitHub

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

Jump to bottom

Improve debugging. #56

Open
r10r opened this issue Jun 10, 2021 · 0 comments
Open

Improve debugging. #56

r10r opened this issue Jun 10, 2021 · 0 comments
Assignees
@r10r
Labels
easy Low hanging fruit enhancement New feature or request

Comments

@r10r
Copy link
Contributor

r10r commented Jun 10, 2021

Debugging is currently not straight forward when lxcri is started through crio.

  1. The logging configuration can only be changed for alllxcri invocations.
  2. Debugging the container using lxcri inspect has to be done on the scheduling node.

Proposal: Use annotations to control debugging. This should work per invocation and without the
need to access the target node.

kubectl run -i --tty ping --annotations org.linuxcontainers.lxcri.Debug  \
--image=busybox --restart=Never --rm --privileged=true --  ping -c100 192.168.1.206

If the annotation org.linuxcontainers.lxcri.Debug is set we could:

  • Enable LogConsole to use ConsoleLogger
  • Set the log level to trace.
  • Log the Runtime configuration when logging is set to trace
  • Log the Container configuration when logging is set to trace
@r10r r10r self-assigned this Jun 10, 2021
@r10r r10r added easy Low hanging fruit enhancement New feature or request labels Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@r10r r10r

Labels
easy Low hanging fruit enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@r10r