Currently, the Bitbucket Pipelines Runner fails to start if the host Docker daemon is set to a logging driver other than json-file (e.g., syslog). Even if the runner container itself is started with --log-driver json-file, it still checks the system-wide default and blocks execution.

Proposed Change

Allow the runner to start as long as the container is using json-file, regardless of the global daemon setting.

Alternatively, support other logging drivers so the runner can operate in restricted enterprise environments where syslog or journald are mandated.

Many companies enforce specific logging drivers for compliance. This requirement forces users to maintain separate, non-standard Docker setups just to run Bitbucket Pipelines.