Repository navigation
fix: create /etc/haproxy with mode 755 in the image - #141
Conversation
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
COPY --chmod=664 spoe-agent.conf /etc/haproxy/spoe-agent.confalso creates the/etc/haproxydirectory with mode 664, without the execute bit. A process that cannot bypass file permissions then cannot openspoe-agent.conf, and HaRP exits at startup withstat() failed for configuration file /etc/haproxy/spoe-agent.conf : Permission denied. This happens when the container runs as a non-root user, and also as root with all capabilities dropped (--cap-drop ALL, orcapabilities: drop: [ALL]in a Kubernetes pod).Changes
/etc/haproxywith mode 755 before it copiesspoe-agent.confinto it.Containers that run as root with the default capabilities are unaffected.