Skip to content

Docker image missing grpcio dependency, but gRPC transport is started unconditionally #563

Description

@phoehnel

Description

The published Docker image (ghcr.io/openagents-org/openagents:latest) fails to start because grpcio isn't installed, even when the gRPC transport isn't needed.

Steps to reproduce

  1. Run the image via docker compose up using the standard docker-compose.yml from the docs.
  2. Container fails to start with:
    [ERROR] Unexpected error: grpcio is required for gRPC transport.
    Install with: pip install openagents[sdk]
    

Root cause

The Dockerfile installs the package without the sdk extra:

RUN pip install --no-cache-dir -e .

grpcio is only pulled in via the [sdk] extra, so it's missing from the runtime image.

Additionally, removing the grpc entry from network.yaml's transports list does not avoid the error — confirmed by running the image with no custom config at all (its own bundled default network.yaml, which also includes grpc in transports). The network appears to require gRPC unconditionally, so this isn't something users can work around purely via config.

Suggested fix

Either:

  • Install .[sdk] (or explicitly grpcio) in the Dockerfile, or
  • Make the gRPC transport genuinely optional, so a config without grpc in transports doesn't require grpcio to be installed.

Environment

  • Image: ghcr.io/openagents-org/openagents:latest (digest sha256:0ea613df2ea9897265c9b13616343ffbd73c24c80abaf303ecda3f95e9765ac9)
  • Deployed via Docker Compose

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions