Doc system test

Container naming

How a container or volume name is built from kind, version id and session, and why names are the routing table.

Meta block front matter of this doc
namespaces
  • durian.cloud/cyanprint/coordinator
type
feature
code
  • sulfone.boron/docker_executor/domain_model.go
  • sulfone.boron/docker_executor/docker.go

Name = cyan-<kind>-<version id without dashes>[-<session>], for example cyan-processor-2222…-s1. Volumes: cyan-<id> (shared blob) and cyan-<id>-<session> (work). All join the cyanprint Docker network, so a name is also the DNS name. A session id with a dash does not parse back reliably.

Where it lives

  • sulfone.boron/docker_executor/domain_model.go
  • sulfone.boron/docker_executor/docker.go

Stub: summary only.