Re: Support for Kubernetes metadata when using docker --log-driver=journald?

2016-05-20 Thread Rich Megginson
On 05/20/2016 10:39 AM, Clayton Coleman wrote: Actually, there may be an issue for this already. https://github.com/kubernetes/kubernetes/issues/15478 I created a new issue: https://github.com/kubernetes/kubernetes/issues/25975 On Fri, May 20, 2016 at 12:38 PM, Clayton Coleman

Re: Support for Kubernetes metadata when using docker --log-driver=journald?

2016-05-20 Thread Clayton Coleman
We could support setting that on the Kubelet when we launch the containers. I think it's reasonable - if you open a Kube issue Derek and I can chime in. On Fri, May 20, 2016 at 12:12 PM, Rich Megginson wrote: > When using OpenShift with the standard docker log driver, there

Re: Support for Kubernetes metadata when using docker --log-driver=journald?

2016-05-20 Thread Clayton Coleman
Actually, there may be an issue for this already. https://github.com/kubernetes/kubernetes/issues/15478 On Fri, May 20, 2016 at 12:38 PM, Clayton Coleman wrote: > We could support setting that on the Kubelet when we launch the > containers. I think it's reasonable - if you

Support for Kubernetes metadata when using docker --log-driver=journald?

2016-05-20 Thread Rich Megginson
When using OpenShift with the standard docker log driver, there are container logs in the following format: /var/log/containers/$name_of_pod-$name_of_project-$name_of_container-$containeruuid.log The fluentd log collector uses $name_of_pod and $name_of_project to look up in k8s additional

Re: Deploying Docker registry

2016-05-20 Thread John McCawley
Thank you for the response. We are still having issues with the network settings. Thanks in advance for the help. Hi, > > I'm doing some integration work with Openshift Origin 1.1.6 and I'm > running across this issue (occurs both with a binary built from source and > using the binary release): >