homepage-fips

packaged by Chainguard

Chainguard Container for homepage-fips

FIPS-compliant Homepage is a highly customizable application dashboard and startpage for managing home server services.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/homepage-fips:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This is the FIPS-enabled variant of the Chainguard Homepage image. It is configured OpenSSL to run in FIPS mode, ensuring all cryptographic operations use only FIPS-approved algorithms.

Getting Started

The container serves the dashboard on port 3000 and reads its YAML configuration (services.yaml, widgets.yaml, bookmarks.yaml, etc.) from a volume mounted at /config. A few environment variables control runtime behavior:

• HOMEPAGE_ALLOWED_HOSTS — comma-separated hostnames (with port, if non-default) you will reach the dashboard from. Recent Homepage releases reject requests from any other host, so in practice this is required.
• PUID / PGID — optional user and group IDs to run as. They default to 0 (root); set them to a non-root UID/GID and the entrypoint fixes ownership of /config and drops privileges via su-exec before starting the server.

Run with docker run

docker run -d --name homepage \
  -e HOMEPAGE_ALLOWED_HOSTS=homepage.example.com \
  -e PUID=1000 -e PGID=1000 \
  -p 3000:3000 \
  -v /path/to/config:/config \
  -v /var/run/docker.sock:/var/run/docker.sock:ro \
  --restart unless-stopped \
  cgr.dev/ORGANIZATION/homepage-fips:latest

The Docker socket mount is optional — include it (read-only, as shown) only if you use Homepage's Docker service-discovery widgets.

Run with Docker Compose

services:
  homepage:
    image: cgr.dev/ORGANIZATION/homepage-fips:latest
    container_name: homepage
    ports:
      - 3000:3000
    environment:
      HOMEPAGE_ALLOWED_HOSTS: homepage.example.com
      PUID: 1000
      PGID: 1000
    volumes:
      - /path/to/config:/config
      - /var/run/docker.sock:/var/run/docker.sock:ro # optional, for Docker integrations
    restart: unless-stopped

Migrating from the upstream image? Upstream mounts configuration at /app/config, while this image uses /config. The entrypoint symlinks the two, so existing /app/config mounts continue to work unchanged.

FIPS Support

This image enforces FIPS 140-3 compliant cryptography at the OpenSSL library level. Non-FIPS algorithms are disabled by default.

Documentation and Resources

• Homepage Official Documentation
• Homepage GitHub Repository
• Chainguard Images Migration Guide

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.