Hi all, thank you for the documentation update. I am sure that would the trick now
On Thursday, 18 February 2016, Eric Wolinetz <[email protected]> wrote: > It was also recently mentioned in a small snippet in the docs under > 'Getting started/Administrators' > > https://docs.openshift.org/latest/getting_started/administrators.html#running-in-a-docker-container > -- in the Note under 'Installing and Starting an All-In-One Server' > > > On Thu, Feb 18, 2016 at 11:52 AM, Luke Meyer <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> We're talking (I thought) about where the node is deployed as a >> container. So this is at docker run time (or atomic). >> >> Scott jumped on this and worked up a PR for the containerized install. >> https://github.com/openshift/origin/pull/7398 >> >> On Thu, Feb 18, 2016 at 12:14 PM, Erik Jacobs <[email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >>> So would this be done via an "oc volume" command? >>> >>> Can this not be made part of the template with a flag? >>> >>> >>> Erik M Jacobs, RHCA >>> Principal Technical Marketing Manager, OpenShift Enterprise >>> Red Hat, Inc. >>> Phone: 646.462.3745 >>> Email: [email protected] >>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>> AOL Instant Messenger: ejacobsatredhat >>> Twitter: @ErikonOpen >>> Freenode: thoraxe >>> >>> On Wed, Feb 17, 2016 at 1:48 PM, Luke Meyer <[email protected] >>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>> >>>> For the containerized install, I am not sure it is documented that you >>>> need to mount /var/log into each node container for fluentd to be able to >>>> get to logs. >>>> >>>> On Sat, Feb 6, 2016 at 11:32 AM, Akram Ben Aissi < >>>> [email protected] >>>> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >>>> >>>>> Hi guys, >>>>> >>>>> I am running a containarized install of OpenShift, and after the >>>>> successful installation of the log centralization with EFK using docs, I >>>>> can get any log search results from Kibana: Every result is empty. >>>>> >>>>> I guess that logging may rely on nodes journalctl output, which is not >>>>> populated apparently in case of container install. >>>>> >>>>> Do you have any tips to make it work: a different configuration for >>>>> the logging template? or a way to redirect the openshift container >>>>> journalctl to the node journalctl? >>>>> >>>>> Greetings >>>>> Akram >>>>> >>>>> >>>>> _______________________________________________ >>>>> dev mailing list >>>>> [email protected] >>>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> dev mailing list >>>> [email protected] >>>> <javascript:_e(%7B%7D,'cvml','[email protected]');> >>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >>>> >>>> >>> >> >> _______________________________________________ >> dev mailing list >> [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');> >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
