The server image is dropping its file capability (inbuxa/inbuxa-server#443, for #424), so it can run in a pod with every capability dropped. Docker already sets net.ipv4.ip_unprivileged_port_start=0 in a container's network namespace; podman doesn't, and without it the server couldn't listen on 25, 443, 465 or 993.
This sets the sysctl on the server service explicitly. It's harmless with today's images (they still have the capability), so it can merge first.
Tested: go test ./... passes; the compose test checks the sysctl is rendered; docker compose run with the same sysctls: block shows 0 inside the container.
The server image is dropping its file capability (inbuxa/inbuxa-server#443, for #424), so it can run in a pod with every capability dropped. Docker already sets `net.ipv4.ip_unprivileged_port_start=0` in a container's network namespace; podman doesn't, and without it the server couldn't listen on 25, 443, 465 or 993.
This sets the sysctl on the server service explicitly. It's harmless with today's images (they still have the capability), so it can merge first.
Tested: `go test ./...` passes; the compose test checks the sysctl is rendered; `docker compose run` with the same `sysctls:` block shows 0 inside the container.
The server image is dropping its file capability (inbuxa-server#424), so a
pod or container with every capability dropped can run it. Docker already
sets net.ipv4.ip_unprivileged_port_start=0 in a container's network
namespace; podman doesn't, and without it the server could no longer
listen on 25, 443, 465 or 993. Set it on the server service explicitly.
Refs inbuxa/inbuxa-server#424
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The server image is dropping its file capability (inbuxa/inbuxa-server#443, for #424), so it can run in a pod with every capability dropped. Docker already sets
net.ipv4.ip_unprivileged_port_start=0in a container's network namespace; podman doesn't, and without it the server couldn't listen on 25, 443, 465 or 993.This sets the sysctl on the server service explicitly. It's harmless with today's images (they still have the capability), so it can merge first.
Tested:
go test ./...passes; the compose test checks the sysctl is rendered;docker compose runwith the samesysctls:block shows 0 inside the container.