Docker-fish

Docker-fish is a Docker image that provides a safe, isolated workspace for testing the Fish shell.

  • Development
  • Tools & Utilities
Docker-fish is a Docker image that provides a safe, isolated workspace for testing the Fish shell. It lets you run and experiment with Fish in a controlled environment without affecting your host system, which is ideal for checking that your scripts and tools work before using them for real.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

49/100 Fair

Maintained
84last commit 5 days ago
Popular
123 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
3
Open issues
1
Last commit
2026-11-16
License
MIT
Activity
steady

Checked yesterday - source: GitHub (pure-fish/docker-fish)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Label services and give them health checks Add the label autoheal: "true" to each service you want watched (or set AUTOHEAL_CONTAINER_LABEL=all for every container), and make sure each one has a healthcheck. Without a label it won't be watched, and without a healthcheck Autoheal usually won't know it has failed. source
  • Mount Docker's control file for Autoheal Run the Autoheal container with /var/run/docker.sock mounted inside it. This local Docker control socket is how Autoheal sees container health and restarts containers; without it, it cannot manage your stack. source
  • Set a startup delay so slow apps don't restart Set AUTOHEAL_START_PERIOD to a reasonable number of seconds, for example 60. This gives slow services time to finish starting up before Autoheal begins restarting them for looking unhealthy. source
  • Running the container Run the default shell with `docker run --interactive --tty --rm purefish/docker-fish`, or pass commands after the image name (for example 'fisher list'). To use a specific Fish version, set the image tag, e.g. purefish/docker-fish:3.5.1. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I start an interactive Fish session with Docker-fish?

Run the image with interactive and tty flags and remove it after exit, using the purefish/docker-fish image. The image starts the Fish shell by default.

How can I run a one-off command in Docker-fish instead of an interactive shell?

Pass the command after the image name, quoting it if needed. The README example runs fisher list with specific package arguments.

How do I test a specific older Fish version?

Set the image tag to the Fish version you want, such as 3.5.1.

Which Fish tools are already available inside the image?

Fisher and Fishtape are installed, and additional packages are listed in the Dockerfile.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads