diff options
author | Thomas Buckley-Houston <tom@tombh.co.uk> | 2018-02-08 18:39:07 +0800 |
---|---|---|
committer | Thomas Buckley-Houston <tom@tombh.co.uk> | 2018-02-08 18:39:07 +0800 |
commit | 2e37da37c40bf604d7a8302f228db71fc1a9e47b (patch) | |
tree | c14b2ef4344ca92b89326e4e84ea59870888458f | |
parent | d2f74cefb8372d2fa3b7b32cda1d115284ba4798 (diff) |
Add gcloud_logger to Dockerfilev0.2.8
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.
-rw-r--r-- | Dockerfile | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -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 |