Run caddy rootless and distroless.

Caddy is a web server written in Go, known for its simplicity and automatic HTTPS features. It acts as a powerful and flexible reverse proxy, handling various protocols like HTTP, HTTPS, WebSockets, gRPC, and FastCGI.

What can I do with this? This image will run caddy rootless and distroless, for maximum security. This image will by default use the JSON format. If you don’t want that but you want to use the Caddyfile format, simply check the compose.yml for the command and make sure your Caddyfile contains at least these settings for the storage and health check to work:

{
	storage file_system /caddy/var
}
127.0.0.1:3000 {
  respond / 200
}

Why should I run this image and not the other image(s) that already exist? Good question! Because ...

If you value security, simplicity and optimizations to the extreme, then this image might be for you.

Below you find a comparison between this image and the most used or original one.

{
	"apps": {
		"http": {
			"servers": {
        "health": {
					"listen": ["127.0.0.1:3000"],
					"routes": [
						{
							"handle": [{
								"handler": "static_response",
								"status_code": 200
							}]
						}
					]
				},
				"demo": {
					"listen": [":80"],
					"routes": [
						{
							"handle": [{
								"handler": "static_response",
								"body": "11notes/caddy"
							}]
						}
					]
				}
			}
		}
	},
  "storage":{
    "module": "file_system",
    "root": "/caddy/var"
  }
}

• /caddy/etc - Directory of your default.json config
• /caddy/var - Directory of all dynamic data

name: "proxy"

x-lockdown: &lockdown
  # prevents write access to the image itself
  read_only: true
  # prevents any process within the container to gain more privileges
  security_opt:
    - "no-new-privileges=true"

services:
  caddy:
    image: "11notes/caddy:2.10.0"
    # use Caddyfile instead of json
    # command: ["run", "--config", "/caddy/etc/Caddyfile"]
    <<: *lockdown
    environment:
      TZ: "Europe/Zurich"
    ports:
      - "80:80/tcp"
      - "443:443/tcp"
    volumes:
      - "caddy.etc:/caddy/etc"
      - "caddy.var:/caddy/var"
      # optional volume (can be tmpfs instead) to store backups of your config
      - "caddy.backup:/caddy/backup"
    networks:
      frontend:
    sysctls:
      # allow rootless container to access port 80 and higher
      net.ipv4.ip_unprivileged_port_start: 80
    restart: "always"

volumes:
  caddy.etc:
  caddy.var:
  caddy.backup:

networks:
  frontend:

These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.

• 2.10.0

It is of my opinion that the :latest tag is dangerous. Many times, I’ve introduced breaking changes to my images. This would have messed up everything for some people. If you don’t want to change the tag to the latest semver, simply use the short versions of semver. Instead of using :2.10.0 you can use :2 or :2.10. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version.

If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!

docker pull 11notes/caddy:2.10.0
docker pull ghcr.io/11notes/caddy:2.10.0
docker pull quay.io/11notes/caddy:2.10.0

• 11notes/caddy

• caddy

This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases for breaking changes. If you have any problems with using this image simply raise an issue, thanks. If you have a question or inputs please create a new discussion instead of an issue. You can find all my other repositories on github.

created 12.08.2025, 00:27:08 (CET)