Release 1.1.0 was pushed as localhost:5000/status-page:latest, on top of 1.0.0. The status container now serves 1.1.0, and you have been asked to put 1.0.0 back. No tag leads to 1.0.0 any more, but ~/RELEASES.md recorded its digest.

Look at what is running and what the tag points at:

docker images --digests
cat ~/RELEASES.md

Pull the old release by digest. Copy the digest from ~/RELEASES.md:

docker pull localhost:5000/status-page@sha256:6b4c4afb1f830937811e6b244d931d02449cbba4aca40c6a5492536093fc7dac

Give it a version tag and push the tag, so the registry has a name for it:

docker tag localhost:5000/status-page@sha256:6b4c4afb1f830937811e6b244d931d02449cbba4aca40c6a5492536093fc7dac localhost:5000/status-page:1.0.0
docker push localhost:5000/status-page:1.0.0
curl -s localhost:5000/v2/status-page/tags/list

Replace the container:

docker rm -f status
docker run -d --name status -p 8080:3000 localhost:5000/status-page:1.0.0
curl -s localhost:8080/health

Leave latest where it is. Fixing which release latest points at is a separate decision.