Replace broken Docker Badge

[MikeMcC399]

Description

Replace broken badge with a text-only link to Docker Hub https://hub.docker.com/_/node/

Node.js Docker images are now well established and it isn't necessary to promote them by adding statistics to the README. Docker Hub itself provides pull & star statistics, that currently show 1B+ and 10K+ which I believe are capped upper limits showing maximum usage.

Motivation and Context

The README contains a Docker badge as its first entry.

The image displays in GitHub through cached content from

https://camo.githubusercontent.com/bec1f70c6e52919eabf93bc17b5311477f1a1a74c6fb4210e8ef0dbd4358ee62/68747470733a2f2f646f636b657269636f2e626c616e6b656e736869702e696f2f696d6167652f6e6f6465

however when viewing a preview of the README.md locally, the badge does not display.

https://dockerico.blankenship.io/image/node returns a 404 error and due to this, the workflow markdown-link-check.yml also now fails on pull requests that update any *.md files.

This is a new issue that was not present in Oct 2025, the last time this workflow previously ran successfully.

https://blankenship.io is a private person domain.
It seems that the service that relied on https://dockerico.blankenship.io is no longer working and there is no help or documentation on that page.

Testing Details

View README

Example Output(if appropriate)

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[MikeMcC399]

Preview

https://github.com/MikeMcC399/docker-node/blob/replace-docker-badge/README.md

[MikeMcC399]

@nschonni

We last interacted together on this area, so perhaps you could take a look at this change? The badge appears to be permanently broken.

[sxa]

Intriguing ... I mentioned in the Yarn PR that the URL seems ok for me but it might be geo-specific as it works from the UK where I am, but not necessarily other locations ...

From the UK on my laptop:

sxa:~$ curl -iL https://dockerico.blankenship.io/image/node
HTTP/2 301 
date: Wed, 04 Feb 2026 11:34:44 GMT
content-length: 0
location: /uk.html
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ebQzUPyzEri%2FTiXcdONio41TruYmgfuHILbCPPHXv5P%2FAl5iitW2MRybp3AvOvY4G3DhBkGWCQLgqjU%2ByaynorI5cNbdtwr1BRnQRInhfgGx0AA9noysDg%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
server: cloudflare
cf-ray: 9c89dc4ee9e71bf8-LHR

HTTP/2 200 
date: Wed, 04 Feb 2026 11:34:44 GMT
content-type: text/html; charset=utf-8
access-control-allow-origin: *

If I do the same from a server in Germany I get an immediate 404 as described in this PR

$ curl -i https://dockerico.blankenship.io/image/node
HTTP/2 404 
date: Wed, 04 Feb 2026 11:32:32 GMT
content-type: text/plain;charset=UTF-8
content-length: 0

[MikeMcC399]

@sxa

How curious!

With VPN to UK https://dockerico.blankenship.io/image/node just forwards to https://dockerico.blankenship.io/uk.html which is not a badge, so unfortunately that it not usable either.

I do think it needs to be dropped. It would need to provide a badge and it's not doing that.

[nschonni]

Thanks, I had noticed this weirdness too, that it renders on GitHub, but falls over hot linking or in CI.

@tianon @yosifkit I didn't see any of the few official images I quickly scanned have a similar badge, so I think it makes sense to drop it, unless you've got a different service/example that this should use

[yosifkit]

@tianon @yosifkit I didn't see any of the few official images I quickly scanned have a similar badge, so I think it makes sense to drop it, unless you've got a different service/example that this should use

We don't have anything we run for Official Images and I don't know of a badge API like this on Docker Hub, so this looks good to me.