Describe the bug
In a self-hosted Agenta deployment using the Helm chart, the services pod fails to start because the container tries to bind to 0.0.0.0:80 while running as a non-root user.
This results in errors like:
connection to ('0.0.0.0', 80) failed: [Errno 13] Permission denied
Can't connect to ('0.0.0.0', 80)
Changing the internal services port to 8080 fixes the issue.
Setup
Self-deployed in Kubernetes using the Helm chart
To Reproduce
- Deploy Agenta in a self-hosted environment using the Helm chart.
- Start the
services component with the default chart values.
- Observe the
services pod logs.
- See that the process fails to bind to port
80 with Permission denied.
Expected behavior
The services component should start successfully with the default chart settings, without requiring a local port override.
Screenshots
No response
Agenta SDK Version
No response
Agenta Image Tag
v0.94.9
Important Context
No response
LinkedIn details
https://www.linkedin.com/in/edufischer/
Describe the bug
In a self-hosted Agenta deployment using the Helm chart, the services pod fails to start because the container tries to bind to
0.0.0.0:80while running as a non-root user.This results in errors like:
Changing the internal services port to
8080fixes the issue.Setup
Self-deployed in Kubernetes using the Helm chart
To Reproduce
servicescomponent with the default chart values.servicespod logs.80withPermission denied.Expected behavior
The
servicescomponent should start successfully with the default chart settings, without requiring a local port override.Screenshots
No response
Agenta SDK Version
No response
Agenta Image Tag
v0.94.9
Important Context
No response
LinkedIn details
https://www.linkedin.com/in/edufischer/