Reload docker logging configuration without daemon restart

Sadly it appears the configuration reload SIGHUP feature does not support all configuration options.

The docs at https://docs.docker.com/v17.09/engine/reference/commandline/dockerd/#miscellaneous-options (See the "CONFIGURATION RELOAD BEHAVIOR" section) tell us the only supported configuration options which can be reloaded in this way are:

The list of currently supported options that can be reconfigured is this:debug: it changes the daemon to debug mode when set to true.cluster-store: it reloads the discovery store with the new address.cluster-store-opts: it uses the new options to reload the discovery store.cluster-advertise: it modifies the address advertised after reloading.labels: it replaces the daemon labels with a new set of labels.live-restore: Enables keeping containers alive during daemon downtime.max-concurrent-downloads: it updates the max concurrent downloads for each pull.max-concurrent-uploads: it updates the max concurrent uploads for each push.default-runtime: it updates the runtime to be used if not is specified at container creation. It defaults to “default” which is the runtime shipped with the official docker packages.runtimes: it updates the list of available OCI runtimes that can be used to run containersauthorization-plugin: specifies the authorization plugins to use.allow-nondistributable-artifacts: Replaces the set of registries to which the daemon will push nondistributable artifacts with a new set of registries.insecure-registries: it replaces the daemon insecure registries with a new set of insecure registries. If some existing insecure registries in daemon’s configuration are not in newly reloaded insecure resgitries, these existing ones will be removed from daemon’s config.registry-mirrors: it replaces the daemon registry mirrors with a new set of registry mirrors. If some existing registry mirrors in daemon’s configuration are not in newly reloaded registry mirrors, these existing ones will be removed from daemon’s config.

Which, as you can see, does not include the log-driver or log-opts configuration parameters.

I'm not aware of a way to reload the logging configuration without a restart, at this time.