conmon
conmon copied to clipboard
containers
An OCI container runtime monitor.
A detailed analysis of the container logging behavior in `conmon` as of tag [`v2.0.28`](https://github.com/containers/conmon/tree/v2.0.28). Summary recommendations: * Match read size to actual `pipe(7)` size (64 KB by default on Linux)...
**Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)** /kind bug **Description** Unable to stop or remove a Podman because of stale exec sessions....
Missing "<timestamp> stdout F" in container log if container terminates without writing a linebreak
**Issue** conmon generates a partial log sequence not conforming to the CRI log spec (https://github.com/kubernetes/community/blob/master/contributors/design-proposals/node/kubelet-cri-logging.md) if container writes a sequence of characters into stdout/stderr and terminates without writing a newline....
continuing conversation [here](https://github.com/cri-o/cri-o/issues/1257)
Currently conmon just truncates the log file when max is reached, this means we loose all of the data. I think we should allow for a backup file. So when...
Release v2.0.22 fails to run under Ubuntu 18.04 with the following error message > Error: failed to connect to container's attach socket: /run/user/205013812/libpod/tmp/socket/7c19123d148494b91f6689e0882d9f2b1b7b7bb8036128bbd4c363c11bbe3044/atta: dial unixpacket /run/user/205013812/libpod/tmp/socket/7c19123d148494b91f6689e0882d9f2b1b7b7bb8036128bbd4c363c11bbe3044/atta: connect: no such file...
I'm trying to use podman-compose to develop a compose file for an application, and I'm having issues when I try to start single containers after `podman-compose up` failed. I'm having...
hello, there's this issue: https://github.com/google/gvisor/issues/2233 The issue is around cri-o and gVisor(runsc) containers using conmon, in the loggs attached to the mentioned issue there seems to be some process closing...
Today `conmon` is engaging in a byte-capture of `stdout`/`stderr` pipes, recording data as a series of JSON documents in a log file. All bytes from both file descriptors are captured...
The repository contains a CHANGELOG file, but the most recent recorded release is 1.0, and the latest release is 2.0.x - would be nice to have updates in there
