No logging output when using default journald logging driver #1523
Comments
|
Same problem... |
|
happy to accept a PR to specify the log driver. Labeling as help wanted. |
|
--log-driver=gelf |
bradrydzewski
added a commit
to bradrydzewski/drone
that referenced
this issue
Jun 22, 2017
bradrydzewski
added a commit
that referenced
this issue
Jun 26, 2017
* fixes #1523 to ensure json-file driver * added environment * inject globals
bradrydzewski
added a commit
that referenced
this issue
Jun 26, 2017
* fixes #1523 to ensure json-file driver * added environment * inject globals * bump version
|
Why is it obvious that Drone would fail to display log output when using the journald driver? One of the best things about upgrading our Drone server from Ubuntu 14.04 to Ubuntu 16.04 was that I could use the journald log driver, not having to choose between system logs (syslog) and docker logs (json). Up until Drone 0.7.1 using the journald driver worked great for me, displaying the Drone build logs in the Drone web ui while at the same time also allowing me to view/search them using journalctl. That broke for me with Drone 0.7.2, which appear to force the json driver? Now I only get the build logs in the web ui. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For obvious reasons Drone fails to log output when using the journald driver in docker by default. However, it is possible in docker to specify logging driver per-container - so if this mode of operation is not supported, sensible default behavior for drone would be to force all containers to start with
log-driver=json.The text was updated successfully, but these errors were encountered: