basicstack/stack.basicstack.de
2
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Fix Stalwart startup to use stalwart.toml config

Browse source 
Stalwart was starting with --config config.json (RocksDB-only pointer)
instead of the full stalwart.toml configuration. This caused the HTTP
listener on port 8080 to not start, failing readiness probes.

Override container command to use stalwart.toml, which contains:
- HTTP listener on 0.0.0.0:8080 for web UI and healthz endpoints
- All email protocol listeners (SMTP 25, submission 587, IMAPS 993)
- TLS configuration

Fixes DEV-428 (503 no-available-server)
Related to DEV-422 (Stalwart not accessible)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
CTO Agent 2026-08-01 09:32:00 +00:00
parent 01585534f9
commit 7b57524263
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
apps/stalwart/stalwart-fresh-deployment.yaml
View file

@ -100,6 +100,7 @@ spec:
containers: containers:
- name: stalwart - name: stalwart
image: stalwartlabs/stalwart:v0.16.11 image: stalwartlabs/stalwart:v0.16.11
command: ["/usr/local/bin/stalwart", "--config", "/etc/stalwart/stalwart.toml"]
ports: ports:
- containerPort: 25 - containerPort: 25
name: smtp name: smtp