You can also run a DaemonSet with minimal resource limits that periodically makes sure the Docker daemon is configured properly, which solves the problem of working across node upgrades.
On Wed, Jun 8, 2016 at 9:09 PM, 'Tim Hockin' via Containers at Google < [email protected]> wrote: > The real downside to doing it this way is that it will be lost when > you do a node upgrade, and any nodes that are added later will not > have this config. > > It's possible for us to find ways to pass flags down to docker, but > it's one of a thousand things we want to work on. Can you explain > exactly what you're trying to set? I have not used docker's log > drivers much, myself... > > On Wed, Jun 8, 2016 at 11:08 AM, 'Alex Robinson' via Containers at > Google <[email protected]> wrote: > > Hi John, > > > > Unfortunately GKE doesn't support configuring the logging driver through > our > > API directly, so you'll have to manually modify each of the nodes in your > > cluster (or use a provisioning tool like salt or puppet) to accomplish > this. > > > > As explained in Docker's documentation, you can do this by passing a > flag to > > the docker daemon when it's started. The flags passed to the docker > daemon > > on GKE nodes are specified in the /etc/default/docker file. You should be > > able to SSH to each node and modify the command line flags in that file > to > > add your preferred logging driver. In order to make the flags take > effect, > > you'll have to kill the docker daemon. It'll automatically restart > within a > > few seconds with the new flag, but this will mean that all the containers > > running on your node will be down for those few seconds, so be careful > that > > such downtime is acceptable before doing this! > > > > Best, > > Alex > > > > > > On Tuesday, June 7, 2016 at 12:20:13 PM UTC-7, John On wrote: > >> > >> We are running Kubernetes with Google Container Engine and I'm wondering > >> if it's possible at all to change the default logging driver for Docker > >> containers? We don't need this at a per-pod level and would prefer a > >> cluster-level configuration. From my limited research it seems like you > can > >> configure the docker-daemon to do so but can anyone give a more detailed > >> explanation on how to modify this? > >> > >> Thanks, > >> John > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Containers at Google" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at https://groups.google.com/group/google-containers. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Containers at Google" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-containers/yU4JycKRBW0/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-containers. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
