Hiya, thank you for publishing Vagrant boxes for macOS! Would it be possible to offer HyperV provided boxes as well? Unfortunately, Docker in Windows relies on HyperV these days, and HyperV is unable to run concurrently with the VirtualBox hypervisor. In other words, developers working with Windows hosts must choose to boot with either HyperV enabled to run Docker, or else HyperV disabled to run VirtualBox and Vagrant. But if the macOS Vagrant boxes were integrated with the HyperV provider, then Windows users would be able to hack on Docker and Vagrant projects at the same time, without having to constantly reboot. What do you think?

Currently, all of our images are based on quite an old version of GoCD Agents (17..).
Upgrade the agents to latest.

I think it will be great to have Docker images that provides Gauge out-of-the-box.

For example, you would create a base image and then use it to create the others in order to support the different language plugins. In the end, the tagging would be a number, corresponding to the actual Gauge version and later on you can choose a term in order to account for the rest of the plugins – read: reporting and "other" plugins. Probably this can be skipped, or just install the most used ones.

This would save time on doing these steps all the time:

FROM golang:1.12.9-stretch

WORKDIR /tmp/workspace/

ADD https://github.com/getgauge/gauge/releases/download/v1.0.5/gauge-1.0.5-linux.x86_64.zip ./

COPY . ./

RUN set -xe \
  && apt-get update \
  && apt-get install -q -y unzip \
  && unzip -o gauge-1.0.5-linux.x86_64.zip -d /usr/local/bin \
  && gauge install html-report --version 4.0.8 \
  && gauge install go --version 0.1.3

UPDATE

In case you consider this one, I think the reporting and "other" plugins part could be ignored; looks like for any Gauge project, once Gauge is installed, one would only need to run gauge install (inside the project's subdirectory) and all the plugins used by that project will be installed – probably from manifest.json. Although if that's the case, it's impossible to pin the version(s), or at least I don't see a way to specify that.