containerd / containerd/containerd
cri: how about let shim save container logs into file directly with k8s log format
- Dominant language
- Go
- Stars
- 21.3k
- Forks
- 4.1k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 97
Description
### What is the problem you're trying to solve
cri:how about let shim save container logs into file directly with k8s log format, containerd doesn't need to participate container's log copy, if containerd exited container init process can still print log to sdtout and containerd use less memory
### Describe the solution you'd like
shim save container logs into file directly with k8s log format
### Additional context
https://github.com/containerd/containerd/pull/13136 I create pr as a demo works well.
_No response_
Contributor guide
Research direction
Start by reviewing the demo pull request at https://github.com/containerd/containerd/pull/13136 and tracing the CRI shim's current container-log handling. Confirm how the proposed change preserves Kubernetes log format and keeps logs available when containerd exits; completion should eliminate containerd's log-copy step without losing stdout or stderr output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100