getgauge-contrib / gauge-docker Goto Github PK

Create a docker image with

• Node js 8+
• Gauge
• Gauge js plugin
• Taiko pre-requiresites for headless chrome

It'd be great to get an updated Taiko dockerfile and regular (automated?) publishing of said images into Docker Hub with appropriate tags and links back to the Dockerfiles.

The current version of this image on Docker Hub has an old version of Gauge, and Taiko 0.2.0 which doesn't appear to be compatible with some of the more recent plugin versions available for Gauge. It also makes using the image a bit laborious, because if you update the built-in Gauge and Taiko yourself it adds several hundred MB to the image size through another layer.

From trying to use this image, I have a few observations

• There are no descriptions or links back to Dockerfiles on Docker hub - it'd be good to provide this as is commonly done for other projects that publish images to Docker Hub. I rarely blindly pull something from Docker Hub - I like to know what I am building on (is it alpine-based? Debian based?)
• Taiko is included inside the image, however the general instructions for Taiko installation (and indeed gauge init js) will add it as a local node_module in your project. This means that when you build on top of this Docker image/Dockerfile so that you can run your tests in a CI environment you end up with two Taiko installations and two Chromium installations, making the image huge.

I would suggest that

• this image is deprecated and repurposed to node.dockerfile and becomes similar to the other Dockerfiles - it's Gauge with nodejs (but excludes Taiko and Chromium itself)
• multi-stage builds are used to produce multiple Docker images from this file; tagged in some standard way, e.g.
  • getgauge/node:latest - Just nodejs + gauge, for people testing Nodejs services, perhaps
  • getgauge/node:chrom-dep - layers on the dependencies to support chrome/chromium
• if we want to get fancy, you could make the node versions explicit
  • getgauge/node:11, getgauge/node:11-chrom-dep or something like that

Although this is not specific to the Taiko/Node/Chromium image

• some kind of automated process is configured to
  • rebuild and publish images regularly for patching from the base images used
  • republish Docker images automatically for new Gauge versions