11notes/kea repository overview

⁠KEA

run kea dhcp rootless.

⁠INTRODUCTION 📢

Kea provides DHCPv4 servers.

⁠SYNOPSIS 📖

What can I do with this? This image will run kea dhcp4 rootless⁠ for more security.

⁠UNIQUE VALUE PROPOSITION 💶

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

• ... this image runs rootless⁠ as 1000:1000
• ... this image is auto updated to the latest version via CI/CD
• ... this image has a health check
• ... this image runs read-only
• ... this image is automatically scanned for CVEs before and after publishing
• ... this image is created via a secure and pinned CI/CD process
• ... this image runs a basic integration test before it will be published (or not if it fails)
• ... this image will automatically create self-signed SSL certificates for the socket connection
• ... this image supports inline configs⁠

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

⁠VOLUMES 📁

• /kea/etc - Directory of your kea config
• /kea/var - Directory of your kea dynamic data

⁠COMPOSE ✂️

name: "kea"

x-lockdown: &lockdown
  # prevents write access to the image itself
  read_only: true

services:
  dhcp4:
    image: "11notes/kea:3.2.0"
    <<: *lockdown
    environment:
      TZ: "Europe/Zurich"
    network_mode: "host"
    volumes:
      - "dhcp4.etc:/kea/etc"
      - "dhcp4.var:/kea/var"
    tmpfs:
      # needed for read-only
      - "/kea/run:uid=1000,gid=1000,mode=0700"
    restart: "always"

volumes:
  dhcp4.etc:
  dhcp4.var:

To find out how you can change the default UID/GID of this container image, consult the RTFM⁠.

⁠DEFAULT SETTINGS 🗃️

⁠ENVIRONMENT 📝

⁠MAIN TAGS 🏷️

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

• 3.2.0⁠
• 3.2.0-unraid⁠
• 3.2.0-nobody⁠

⁠There is no latest tag, what am I supposed to do about updates?

It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you don’t want to change the tag to the latest semver⁠, simply use the short versions of semver⁠. Instead of using :3.2.0 you can use :3 or :3.2. 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. Which in theory should not introduce breaking changes.

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!

⁠REGISTRIES ☁️

docker pull 11notes/kea:3.2.0
docker pull ghcr.io/11notes/kea:3.2.0
docker pull quay.io/11notes/kea:3.2.0

⁠UNRAID VERSION 🟠

This image supports unraid by default. Simply add -unraid to any tag and the image will run as 99:100 instead of 1000:1000.

⁠NOBODY VERSION 👻

This image supports nobody by default. Simply add -nobody to any tag and the image will run as 65534:65534 instead of 1000:1000.

⁠SOURCE 💾

• 11notes/kea⁠

⁠PARENT IMAGE 🏛️

• [${{ json_readme_parent_image }}](${{ json_readme_parent_url }})

⁠BUILT WITH 🧰

• kea⁠
• 11notes/util⁠

⁠GENERAL TIPS 📌

• Use a reverse proxy like Traefik, Nginx, HAproxy to terminate TLS and to protect your endpoints
• Use Let’s Encrypt DNS-01 challenge to obtain valid SSL certificates for your services

⁠ElevenNotes™️

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 25.06.2026, 06:27:52 (CET)