I will paste a github repo here (GitHub - kaijietti/loop: To reproduce a bug when using docker and fluentd.) which can reproduce this bug. I am not familiar with Docker so i don’t know what’s happening.
bump! Need some help.
Please describe the actual bug. I don’t expect many people cloning the repository and trying to reproduce the issue which might not happen in different environments. Since you only mentioned the repository can reproduce the issue but not that you described the issue there, it is understandable that you didn’t get the attention of anyone yet. I almost asked for describing the issue too., but even now I don’t completely understand it and I wouldn’t run failing commands and spend time on understanding what is happening.
You mention t0 and t11 but not what that means so we have to find it… I leave this link here for others:
Please, share the relevant information directly on the forum next time to make it easier for everyone to help you.
The fact that the loop container doesn’t have any output could be a fluentd driver bug. I don’t know how exactly that driver works, but the container will continue trying to send logs to the stopped fluentd and it is possible that the standard output breaks too.
CTRL+C stops the container only if the process in the container handles the stop signal. I don’t see that in your Go code, but it could be that I just don’t recognize it.
Removing the container means you also need to stop it. If nothing handles the stop signal, Docker normally kills the process in 10 seconds by default but that timeout can be chaanged. If Docker can’t handle that either because it is already in a state where constantly doing something else, that could lead to tthe situation you had, but this is just a guess. Since restarting the Docker daemon helped, You could try to check the daemon logs.
systemctl status docker
journalctl -e -u docker