1.0.2

Dockerfile

@@ -16,6 +16,31 @@ RUN apt-get update && apt-get install -y wget --no-install-recommends \
     && apt-get purge --auto-remove -y curl \
     && rm -rf /src/*.deb
 
+RUN echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections \
+    && apt-get update \
+    && apt-get upgrade --no-install-recommends -y \
+    && apt-get install -y -q --no-install-recommends \
+        software-properties-common \
+        apt-transport-https \
+        build-essential \
+        ca-certificates \
+        curl \
+        g++ \
+        gcc \
+        git \
+        make \
+        openssl \
+        python \
+        rsync \
+        ssh \
+        wget \
+    && curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - \
+    && echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list \
+    && apt-get update \
+    && apt-get install yarn -y \
+    && apt-get clean \
+    && rm -r /var/lib/apt/lists/*
+
 # It's a good idea to use dumb-init to help prevent zombie chrome processes.
 ADD https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 /usr/local/bin/dumb-init
 RUN chmod +x /usr/local/bin/dumb-init

package.json

@@ -1,7 +1,7 @@
 {
   "name": "ht-docker-chrome",
   "private": true,
-  "version": "1.0.1",
+  "version": "1.0.2",
   "description": "chrome for docker",
   "main": "index.js",
   "scripts": {