Ask HN: My Docker image just hit 1M+ pulls. What now?

7 points by alpeware ↗ HN
Here's some context. Sometime in May 2017 I was following the Chrome headless dev closely and wanted to use the most up to date build. As I wasn't able to find a regularly updated Docker image on the Hub, I decided to build my own [0]. I sent a short announcement to the headless-dev mailing list [1] and 10 months later the image hit 1M+ pulls. Just for fun, I've been collecting the pull count on a regular basis [2].

I'd like to make some changes to the image (remove the custom certificates feature, update the base image etc.) plus any other features that might be useful. The source repository is hosted on Github [3] and there have been 2 pull requests to date, so not much data to go with.

I'm looking for ideas how I could best get in touch with everyone who is using the image, how to collect feedback going forward and any other suggestions the HN community might have for the future direction of this project.

Thanks!

-alpeware

---

[0] https://hub.docker.com/r/alpeware/chrome-headless-trunk/

[1] https://groups.google.com/a/chromium.org/d/msg/headless-dev/ntHnXHBvHaI/lP0Jw-laAwAJ

[2] https://docs.google.com/spreadsheets/d/e/2PACX-1vQMZcFPvH92Vptpj5gz3WX-z-fe3F0ycVP3cb9IGS91NO4wOAbt4kx5tYu9KeuDPkVa5cybS8CLXSe5/pubhtml?gid=905813765&single=true

[3] https://github.com/alpeware/chrome-headless-trunk

1 comment

[ 3.2 ms ] story [ 16.1 ms ] thread
Some ideas -

- add a message to the start script encouraging users to sign up for a mailing list if they want to receive updates and hope it shows up in the logs

- generalize the ability to auto-update a public docker image as a service