Godon Images

Container images built with Nix for reproducible, isolated builds.

Images

Image	Language	Port	Purpose
godon-api	Rust (Axum)	8080	REST API for managing optimizer breeders and credentials
godon-cli	Rust	-	CLI tool for interacting with godon-api
godon-observer	Rust (Hyper)	8089	Optimization observability: Prometheus metrics, trial history from Optuna storage, visualization dashboard
godon-seeder	Rust	-	Deploys controller/breeder scripts to Windmill
godon-mcp	Rust (Axum)	3001	MCP server exposing godon-api as tool interface for LLM agents
godon-bench-greenhouse	Rust (Axum)	8090	Multi-zone greenhouse simulation bench for engine verification

Structure

godon-images/
├── build/                           # Shared build infrastructure
│   ├── Dockerfile.nix-builder       # Isolated Nix builder container
│   └── build-container-nix.sh       # Build script (uses dockerTools.buildLayeredImage)
├── images/                          # Service images (one directory per image)
│   ├── godon-api/
│   ├── godon-cli/
│   ├── godon-observer/
│   ├── godon-seeder/
│   ├── godon-mcp/
│   └── godon-bench-greenhouse/
├── shared/                          # Shared test infrastructure
│   └── tests/                       # Windmill test stack, stub scripts, test data

Building

cd images/<image-name>
../../build/build-container-nix.sh --version <version> --name <image-name>

Releasing

Push a tag in the format <image-name>-X.Y.Z (e.g., godon-mcp-0.0.1). GitHub Actions workflows handle the rest — each image has a <image>-ci.yml for PR builds and a <image>-release.yml triggered by the tag, which delegates to the shared release-image.yml to build and push to ghcr.io/godon-dev/<image-name>.

Architecture

• Isolated Nix builds: Each service builds in an isolated container to avoid Nix sandboxing issues
• Reproducible containers: Nix ensures exact same dependencies everywhere
• Simple structure: Focus on container building without unnecessary complexity
• Extensible: Easy to add new services following the same pattern