dufs

packaged by Chainguard

Chainguard Container for dufs

A file server that supports static serving, uploading, searching, accessing control, webdav...

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/dufs:latest

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

Compatibility Notes

Chainguard's dufs container image is comparable to the upstream image, with the following differences:

• Like all other Chainguard Containers, dufs features a stripped down, minimal design
• It has few-to-zero CVEs
• It does not run as the root user; the default runtime user is nonroot (UID 65532)

The entrypoint is /bin/dufs, and the container stops on SIGINT, matching upstream. The image tracks the latest upstream dufs release, a Rust application dual-licensed under MIT or Apache License 2.0.

Getting Started

Serve a local directory over HTTP on the default port 5000:

docker run --rm -p 5000:5000 \
  -v "$(pwd)":/data \
  cgr.dev/ORGANIZATION/dufs:latest /data

Then browse to http://localhost:5000.

Enable all operations (upload, delete, search, WebDAV, and so on):

docker run --rm -p 5000:5000 \
  -v "$(pwd)":/data \
  cgr.dev/ORGANIZATION/dufs:latest /data -A

When you enable uploads or other write operations, the mounted directory must be writable by UID 65532.

Restrict access with credentials:

docker run --rm -p 5000:5000 \
  -v "$(pwd)":/data \
  cgr.dev/ORGANIZATION/dufs:latest /data -A -a admin:pass@/:rw

Serve over HTTPS with your own certificate and key. Mount the certificates outside the served directory, and mount them read-only. dufs serves every file under the served path, so a key stored there could be downloaded by anyone who can reach the server:

docker run --rm -p 5000:5000 \
  -v "$(pwd)/data":/data \
  -v "$(pwd)/certs":/certs:ro \
  cgr.dev/ORGANIZATION/dufs:latest /data \
  --tls-cert /certs/cert.pem --tls-key /certs/key.pem

The key file must be readable by UID 65532, the default runtime user.

Configuration

• Exposed ports: dufs listens on port 5000 by default (change with -p). The image does not declare an EXPOSE.
• Volumes: none are declared; bind-mount the directory you want to serve (for example at /data) and pass its path as the argument.

Run dufs --help for the full list of options.

Documentation and Resources

• dufs GitHub Repository

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.