Public access is read-only; account registration on this server is disabled. Report issues at https://github.com/k2patel/docker-flood-client/issues. For contributions, open an issue with a link to your branch or patch on another Git provider. Changes are reviewed and applied by the maintainer on Gitea.

Gitea Actions publishes docker.io/k2patel/floodui:latest only on manual runs. Select main in Actions → Build and Push Custom Flood Image → Run workflow and set the required flood_version release tag. The configured release is v4.16.2. Repository pushes do not trigger builds.

This is a Flood-only image using the custom Dockerfile.client: it runs the Flood web UI/API and connects to an external torrent service. It does not bundle or start rTorrent. The Dockerfile uses the upstream pnpm lockfile and builds the server and client assets; changing release families may require updating the build tooling.

Set Actions secrets DOCKER_USERNAME and DOCKER_TOKEN with Docker Hub write access to k2patel/floodui. Builds run remotely on the Kubernetes runner for linux/amd64, pushing directly to Docker Hub. Images are not loaded into the runner image store, and the temporary builder and cache are removed afterward. No image archives or build records are uploaded to Gitea, and no local container builds are required.

Base image: Node.js 24 on Alpine Linux 3.24 stable (node:24-alpine3.24), including the latest patch updates in those release series.

The image build starts the actual Flood server and requires HTTP 200 before publishing; it does not start a torrent daemon.