dideler/docker-fish-shell

🐳🐟🐚Docker image for the Friendly Interactive Shell, aka fish

docker-fish-shell's Issues

Auto-build and push image

Can create a workflow via GitHub Actions to do this whenever we push Dockerfile changes to master.

Besides reducing maintenance steps, it's also safer to build the image on a clean non-development environment.

GitHub docs

Decide if DockerHub should still be supported

Related to #1.

As of yesterday, May 1st 2021, it's been six months since the new DockerHub retention policy was introduced. That means they will start deleting stale images (6 months or older without push/pull activity) from now on.

All the images were still present today. Not sure if they gave a grace period, since I doubt all versions have been pulled in the last six months. They'll be present for at least another six months because I pulled them all today.

Decide if it's worth the maintenance hassle to continue using DockerHub in addition to GitHub Container Registry.

One benefit is that a lot of tooling defaults to DockerHub for images.

Also consider creating a GitHub action that runs very infrequently (like once every six months) to reset the counter.
Need to do docker pull --all-tags dideler/fish-shell more or less.

Start using GitHub Container Registry

Effective Nov 1st 2020, Docker is introducing a container image retention policy for inactive images.

An inactive image is a container image that has not been either pushed or pulled from the Docker Hub image repository in 6 or more months. Free plans will have a 6 month inactive image retention limit.

Backup existing images to a GitHub registry and start using GitHub as the primary registry for new images.

GitHub Container Registry is superseding GitHub Packages Docker registry. During the beta of GitHub Container Registry, storage and bandwidth is free.