98ed2e8606
This was originally submitted to pick up v0.3.1 of the cloud logging plugin which had a fix for the name 'metadata' failing to resolve. Since new releases of google-fluentd have this fix, it is no longer required. I've done some additional testing of 'gem update' behavior in the interim and I think it is ok to use in targeted situations, but we should not be doing an unconstrained update in general. The issue is that updating a gem may bring new dependencies, some of those dependencies may include native code, so it may try to launch a compiler, which isn't desirable and prone to failure. If we do need to grab an updated gem in the future we should specify an explicit version and the --minimal-deps flag.
28 lines
1.1 KiB
Docker
28 lines
1.1 KiB
Docker
# This Dockerfile will build an image that is configured
|
|
# to use Fluentd to collect all Docker container log files
|
|
# and then cause them to be ingested using the Google Cloud
|
|
# Logging API. This configuration assumes that the host performning
|
|
# the collection is a VM that has been created with a logging.write
|
|
# scope and that the Logging API has been enabled for the project
|
|
# in the Google Developer Console.
|
|
|
|
FROM ubuntu:14.04
|
|
MAINTAINER Satnam Singh "satnam@google.com"
|
|
|
|
# Disable prompts from apt.
|
|
ENV DEBIAN_FRONTEND noninteractive
|
|
|
|
RUN apt-get -q update && \
|
|
apt-get install -y curl && \
|
|
apt-get clean && \
|
|
curl -s https://storage.googleapis.com/signals-agents/logging/google-fluentd-install.sh | sudo bash
|
|
|
|
# Copy the Fluentd configuration file for logging Docker container logs.
|
|
COPY google-fluentd.conf /etc/google-fluentd/google-fluentd.conf
|
|
|
|
# Install the record reformer plugin.
|
|
RUN /usr/sbin/google-fluentd-gem install fluent-plugin-record-reformer
|
|
|
|
# Start Fluentd to pick up our config that watches Docker container logs.
|
|
CMD /usr/sbin/google-fluentd "$FLUENTD_ARGS" > /var/log/google-fluentd.log
|