Image that runs with all capabilities dropped #424

Closed
opened 2026-11-18 05:14:37 +00:00 by jcoffey-dev · 5 comments
Owner

K-S1 · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts)

Kubernetes 'restricted' pods drop ALL capabilities. Today the binary carries a file capability, so exec fails unless NET_BIND_SERVICE is added back. Drop the file capability, make listener ports configurable by environment so the chart can use high ports, and keep Docker users working through port mapping.

Done when

  • The image starts with --cap-drop ALL and nothing added
  • Default listeners for Docker/Compose users documented and unchanged in behaviour
  • UPGRADING note if anything changes for existing installs

Depends on: S1

**K-S1** · size S · part of inbuxa for Kubernetes (tracking issue in inbuxa-charts) Kubernetes 'restricted' pods drop ALL capabilities. Today the binary carries a file capability, so exec fails unless NET_BIND_SERVICE is added back. Drop the file capability, make listener ports configurable by environment so the chart can use high ports, and keep Docker users working through port mapping. **Done when** - The image starts with `--cap-drop ALL` and nothing added - Default listeners for Docker/Compose users documented and unchanged in behaviour - UPGRADING note if anything changes for existing installs **Depends on:** S1
jcoffey-dev added this to the 27.1 milestone 2026-11-18 05:14:37 +00:00
jcoffey-dev added the security
priority
p1
enhancement
labels 2026-11-18 05:14:38 +00:00
Author
Owner

Spike result (inbuxa-k8s-lab S1): with the file capability removed, rc.22 runs with all capabilities dropped, no-new-privileges and a read-only root (tmpfs on the two volumes and /tmp). So the change here is:

  1. Drop setcap from the Dockerfile (or keep it only in a Docker-flavoured tag; decision is one image).
  2. Give the chart a way to put mail listeners on high ports on first start. Listeners live in the store, so either env-driven defaults for a fresh store or a documented setup step the chart runs.
  3. Docker/Compose users: port mapping keeps 25/465/587/… outside; UPGRADING note for anyone who relied on binding low ports inside the container.
Spike result (inbuxa-k8s-lab S1): with the file capability removed, rc.22 runs with all capabilities dropped, no-new-privileges and a read-only root (tmpfs on the two volumes and `/tmp`). So the change here is: 1. Drop `setcap` from the Dockerfile (or keep it only in a Docker-flavoured tag; decision is one image). 2. Give the chart a way to put mail listeners on high ports on first start. Listeners live in the store, so either env-driven defaults for a fresh store or a documented setup step the chart runs. 3. Docker/Compose users: port mapping keeps 25/465/587/… outside; UPGRADING note for anyone who relied on binding low ports inside the container.
jcoffey-dev self-assigned this 2026-11-18 06:28:57 +00:00
Author
Owner

Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.

Folded into the checklist on inbuxa/inbuxa-charts#14 to keep the issue list short. The details stay here; reopen this when work on it starts.
Author
Owner

Reopened: work on this is in progress.

Reopened: work on this is in progress.
Author
Owner

In PR #443. Companion PRs: inbuxa/inbuxa-installer#80 (sysctl in compose for podman) and the docs PR on inbuxa/inbuxa.org.

In PR #443. Companion PRs: inbuxa/inbuxa-installer#80 (sysctl in compose for podman) and the docs PR on inbuxa/inbuxa.org.
Author
Owner

Fixed in #443, merged to main; ships in the next 27.1 release candidate.

Fixed in #443, merged to main; ships in the next 27.1 release candidate.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-server#424