From 2e37da37c40bf604d7a8302f228db71fc1a9e47b Mon Sep 17 00:00:00 2001 From: Thomas Buckley-Houston Date: Thu, 8 Feb 2018 18:39:07 +0800 Subject: [PATCH] Add gcloud_logger to Dockerfile This is used on the Browsh as a Service platform for anonymous logins, it does not get used by default unless explicitly called. It is an external third-party binary and not at all integrated with the browsh binary itself. The situation is that browsh logs to a file *inside docker* so for now the easier way to get at those logs is to include this tool inside the docker container as well. I'm sure there are ways to completely separate the concerns here and I hope to do that soon once I settle on the final infrastructure for BaaS. --- Dockerfile | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Dockerfile b/Dockerfile index 772ed1b..4839f0a 100644 --- a/Dockerfile +++ b/Dockerfile @@ -1,6 +1,13 @@ FROM bitnami/minideb:stretch RUN install_packages xvfb libgtk-3-0 curl ca-certificates bzip2 libdbus-glib-1-2 + +# Logging client for Google's Stackdriver logging service. +# NB Not used by default. Only used by the Browsh as a Service platform on the +# anonymous accounts. +RUN curl -L -o /usr/local/bin/gcloud_logger https://github.com/tombh/gcloud_pipe_logger/releases/download/v0.0.5/gcloud_pipe_logger_0.0.5_linux_amd64 +RUN chmod a+x /usr/local/bin/gcloud_logger + RUN useradd -m user RUN su user ENV HOME=/home/user