Skip to content

Allow NET_BIND_SERVICE (file capability on the binary) #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bulbashenko merged 1 commit into from
Oct 12, 2026
Merged

Allow NET_BIND_SERVICE (file capability on the binary) #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions deploy/k8s/stalwart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,10 @@ spec:
requests: { cpu: 50m, memory: 192Mi }
limits: { memory: 1Gi }
securityContext:
allowPrivilegeEscalation: false
capabilities: { drop: [ALL] }
# The binary carries the file capability cap_net_bind_service; exec fails (EPERM) unless it
# can be granted. Everything else stays dropped.
allowPrivilegeEscalation: true
capabilities: { drop: [ALL], add: [NET_BIND_SERVICE] }
volumeMounts:
- { name: config, mountPath: /etc/stalwart }
# Scratch space and the file tracer (/var/lib/stalwart/logs); nothing durable lives here.
Expand Down
Loading