konoui issues

Results 6 issues of


                                            konoui

fix format string for ecs-init logging

### Summary fix format string for ecs-init log. ### Implementation details using "%t" instead of "%s". Currently, ecs init outputs a following log ``` [INFO] pre-start: ecs agent container image...

Feature Request: verify container image platform

Thank you for making a great tool! I would like to propose a platform verify feature. ### Background Currently, ECS provides several runtimes. e.g. Fargate/EC2 with AMD64/Linux Fargate/EC2 with ARM64/Linux...

fix shim logger exit on stream.Log() error to prevent container halt

*Issue #, if available:* #253 *Description of changes:* * To avoid shim logger termination, which impacts container availability, the logger.Log method always returns nil. * Instead of returning an error,...

When the Docker.Log() method returns an error, it affects the availability of application containers

[When the Docker.Log() method returns an error](https://github.com/aws/shim-loggers-for-containerd/blob/main/logger/common.go#L523), the shim logger binary exits with a status of zero. As a result, the app container halts indefinitely due to blocked stdout/stderr pipes....

fix: adjust buffer size for awslogs driver in non-blocking mode

*Issue #, if available:* #239 *Description of changes:* The buffered logger uses `maximumBytesPerEvent` instead of `defaultAwsBufSizeInBytes` to avoid unexpected log splitting. Before the fix, the e2e test failed with `a...

Unexpected splitting of logs in the awslogs driver in non-blocking mode when a container outputs a log larger than 256KiB

Scenario: A container with non-blocking mode outputs a log of 256KiB + 1byte (262145bytes). ```json { "containerDefinitions": [ { "name": "app", "image": "amazonlinux:2", "cpu": 0, "portMappings": [], "essential": true, "command":...