Certain log configuration reliably triggers a segfault #47709
Labels
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
status/0-triage
Description
A segfault occurs reliably under these circumstances:
fluentd-async
option is provided and istrue
.Reproduce
Run this:
View dockerd logs (e.g.
sudo journalctl -u docker.service
) and observe that the daemon has been restarted due to a segfault.Expected behavior
Docker should error/warn, but not segfault.
docker version
Client: Docker Engine - Community Version: 26.0.0 API version: 1.45 Go version: go1.21.8 Git commit: 2ae903e Built: Wed Mar 20 15:17:48 2024 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 26.0.0 API version: 1.45 (minimum version 1.24) Go version: go1.21.8 Git commit: 8b79278 Built: Wed Mar 20 15:17:48 2024 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.28 GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb runc: Version: 1.1.12 GitCommit: v1.1.12-0-g51d5e94 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Additional Info
It may be related to this open issue in fluentd.
Relevant part of my dockerd logs (
sudo journalctl -u docker.service
):The text was updated successfully, but these errors were encountered: