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
Pods not always creating logs #10065
Comments
That's not what you showed. You showed that the log files are being created, but contain no output. Can you replicate this with a test pods whose container is guaranteed to produce output on stdout or stderr? It seems more likely that your containers just aren't writing any log output. I'm not aware of any issues with containerd where it fails to collect output from containerized processes. Can you also confirm that you're using the embedded containerd, and not docker or some other container runtime? |
Environmental Info:
K3s Version: v1.28.8+k3s1 (653dd61) | go version go1.21.8
Node(s) CPU architecture, OS, and Version: Linux orangepizero3 6.1.31-sun50iw9 #1.0.2 SMP Thu Sep 28 14:15:40 CST 2023 aarch64 aarch64 aarch64 GNU/Linux
Cluster Configuration: Just one node!
Describe the bug:
I'm creating some pods but the problem is that NOT ALWAYS the pods create logs files. Even with the same configuration, I have to kill a pod and wait that the deployment create a new one until I see logs.
I also checked /var/log/pods directly in the node and I get empty files
Example:
Then I restart the pod many times, and..
This happens while creating pods with kubectl apply or argocd
Steps To Reproduce:
Expected behavior:
Every time that a pod is created, the logs file should be created.
Actual behavior:
Pod logs are not consistent since many times they are not even created.
The text was updated successfully, but these errors were encountered: