com.atlassian.pipelines.runner.core.exception.PrerequisiteFailedRunnerException: The docker logging

[Luis Plaza]

[luis@fedora]$ docker info --format '{{.LoggingDriver}}'

journald

[luis@fedora ldap]$ sudo docker container run -it -v /tmp:/tmp -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker/containers:/var/lib/docker/containers:ro -e ACCOUNT_UUID={xxxxxx-xxxxxx-xxxxx-xxxx-xxxxx} -e REPOSITORY_UUID={xxxxx-xxxx-xxxx-xxxx-xxxxx} -e RUNNER_UUID={xxxx-xx-xxx-xx-xxx} -e RUNTIME_PREREQUISITES_ENABLED=true -e OAUTH_CLIENT_ID=xxxxx -e OAUTH_CLIENT_SECRET=xxxx -e WORKING_DIRECTORY=/tmp --log-driver json-file --log-opt max-size=10m --network host --name bitbucket-import-runner docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner
+ ./entrypoint.sh
[2021-11-02 10:55:45,130] Runner version: 1.184
[2021-11-02 10:55:45,150] Runner runtime: linux-docker
[2021-11-02 10:55:46,590] Copying Docker cli to working directory.
Exception in thread "main" com.atlassian.pipelines.runner.core.exception.PrerequisiteFailedRunnerException: The docker logging driver must be json-file.

Hi ! Please, how can I set the runner to use a different logging-driver to do not get this error? I am using moby-engine

[lassian]

Hi Luis,

We only support the json-file logging driver on the hosts docker daemon as we read the containers (build, clone and any services) json log files to upload them to our services.

Follow the instructions here to change the logging driver on the host https://docs.docker.com/config/containers/logging/configure/#:~:text=To%20configure%20the%20Docker%20daemon,dockerd%20reference%20manual%20for%20details.

Kind Regards,

Nathan

[Hervé Nicol]

Hi,

I have the same issue, and I am disapointed the whole daemon has to be set to json-file logging.

Logging driver can be set per-container. So bitbucket-runner could set it to `json-file` for the containers it starts.

I think that would be a great improvement.