Skip to content

[Bug] Services container fails in self-hosted Helm deployment because it binds to privileged port 80 as non-root #4063

@eduardofischer

Description

@eduardofischer

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

  1. Deploy Agenta in a self-hosted environment using the Helm chart.
  2. Start the services component with the default chart values.
  3. Observe the services pod logs.
  4. 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/

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions