Public registries typically work without credentials; some images may require authentication or be rate-limited. Private registries require authentication configured in credentials.
Managing via UI
Navigate to Configuration → Registry Connections in the AgentSystems UI at http://localhost:3001. The UI allows you to:- Add public and private registries
- Configure authentication methods
- Enable/disable registry connections
Configuration Structure
Each registry connection requires:| Field | Description | Required |
|---|---|---|
url | Registry hostname (e.g., docker.io, ghcr.io) | Yes |
enabled | Whether this connection is active | Yes |
auth.method | Authentication type: none, basic, bearer | Yes |
auth.username_env | Environment variable for username (basic auth) | No |
auth.password_env | Environment variable for password (basic auth) | No |
auth.token_env | Environment variable for token (bearer auth) | No |
Manual Configuration
Editagentsystems-config.yml directly:
Registry Usage in Agent Configuration
Agents reference registry connections when specifying their image source:Authentication Methods
None
None
For public registries and images. No credentials required.
Basic
Basic
Username and password/token authentication. Used by Docker Hub, GHCR, and many private registries.
Bearer
Bearer
Token-based authentication. Common for enterprise registries.

