Re: docker: ensure runit logging works.

Re: docker: ensure runit logging works.

[jbenden]

[-- Attachment #1: Type: text/plain, Size: 163 bytes --]

New comment by jbenden on void-packages repository

https://github.com/void-linux/void-packages/pull/19115#issuecomment-586456093

Comment:
Absolutely! Thank you!

Re: [PR PATCH] [Merged]: docker: update to 19.03.6 and ensure runit logging works.

[xtraeme]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

There's a merged pull request on the void-packages repository

docker: update to 19.03.6 and ensure runit logging works.
https://github.com/void-linux/void-packages/pull/19115

Description:
This patch captures all Docker logging output and forwards to the runit logging system.

In order to accomplish this goal, both an update to the runit log service and a default Docker daemon configuration were needed. I believe the top line of the `daemon.json` is required; however, the other two lines are just plainly super useful - to the point of being desirable for inclusion as the default configuration...

Signed-off-by: Joseph Benden <joe@benden.us>

Re: docker: update to 19.03.6 and ensure runit logging works.

[D-Nice]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

New comment by D-Nice on void-packages repository

https://github.com/void-linux/void-packages/pull/19115#issuecomment-586746972

Comment:
I would consider this patch far from ideal, as it overrides set config of users and could be a danger... It overrode my config which has a bunch of security additions.

Re: docker: update to 19.03.6 and ensure runit logging works.

[D-Nice]

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

New comment by D-Nice on void-packages repository

https://github.com/void-linux/void-packages/pull/19115#issuecomment-586749142

Comment:
A much more unobtrusive solution would be to pass these apparently needed options as flags via a conf in the runit service directory, or even directly within the runit service itself. All 3 directives are supported as flags. It is much more likely someone is utilizing daemon.json already, rather than the runit conf.