First off all I am not sure if this is the right category. If it is not, feel free to move it. »Help« seemed wrong as I do have a workaround.
Drone should set the log-driver for all its spawned containers explicitly because if the Docker deamon using the fluentd logdriver causes drone builds to exit with error 255.
After switching the docker deamon to use the fluendt-logdriver our builds fail with this error from the container
[error] Error streaming docker logs for plugins/drone-cache:latest. Unrecognized input header
It also breaks the slack-integration and there are no messages at all in the drone-build-»terminal«
As soon as we use the standard json-file logdriver everything works fine.
$ docker info
Server Version: 1.11.1
Storage Driver: overlay
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Network: null host bridge
Kernel Version: 4.4.0-0.bpo.1-amd64
Operating System: Debian GNU/Linux 8 (jessie)
Total Memory: 31.24 GiB
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
WARNING: No kernel memory limit support
Of course one can set the logdriver individually for every container outside of the build-process to fluendt as a workaround but i guess drone could as well explicitly set theirs to json-file and that would be more foolproof.
Should I give more details or can I open a github issue for this?
I could as well attach it to this one about the same feature: