Releases: emilio-martinez/docker-chrome-node-yarn
v1.1.0
The image is published in Docker as popcornpool/chrome-node-yarn:1.1.0.
This release adds AWS CLI support, since it's a common tool to be used within CI workflows. Additionally, Chrome, Node, npm, and yarn are all updated. Note that in the case of npm, it's updated to the latest version included within Node 8 LTS.
> $CHROME_BIN --version
Google Chrome 66.0.3359.170
> node --version
v8.11.2
> npm --version
5.6.0
> yarn --version
1.6.0
> aws --version
aws-cli/1.11.13 Python/3.5.2
v1.0.0
1.0 🎉
This release simply marks a point in time where this Docker image is in a generally good spot to start using, testing, and evaluating further. This release adds one relatively minor change: the working directory upon running the image will be user's home directory, which is exposed via the $HOME
variable.
The image is published in Docker as popcornpool/chrome-node-yarn
and will be auto-built with every release.
As a quick backstory, after a while of being a Docker image consumer, I decided to set up my own image for the first time to use on a few projects where I saw this recurring need. Docker's deceptively simple, but it definitely has a few tricks up its sleeve. I explored a few different paths to achieve the initial goals for this Docker image, iterated on them, ironed out some kinks on the potential candidates, and finally landed on what you see on this release. It's nice to try new things, right?!
> $CHROME_BIN --version
Google Chrome 63.0.3239.132
> node --version
v8.9.4
> npm --version
5.6.0
>yarn --version
1.3.2
v1.0.0-beta.3
The Docker image has changed to use selenium/standalone-chrome
as a base instead of having node:8
. This should provide more control over what binary versions are actually provided by this image. For example, freezing the version of yarn
—if for any reason we ever needed to—is substantially easier. Additionally, the image size has dropped from 452 MB
to 397 MB
.
> $CHROME_BIN --version
Google Chrome 63.0.3239.132
> node --version
v8.9.4
> npm --version
5.6.0
>yarn --version
1.3.2
v1.0.0-beta.1
Super minor iteration. Setting the user to a non-privileged one, which should make Chrome happier.
v1.0.0-beta.0
> $CHROME_BIN --version
Google Chrome 63.0.3239.132
> node --version
v8.9.4
> npm --version
5.6.0
> yarn --version
1.3.2