File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 1+ # compose2pod 0.1.4 — accept the service ` container_name ` key
2+
3+ A patch release that stops rejecting valid compose documents which set a
4+ service ` container_name ` . The validator was over-strict: a service carrying
5+ ` container_name: ` — used to give a service a stable name that other services
6+ connect to — raised ` unsupported key 'container_name' ` . Such documents now
7+ convert.
8+
9+ ## Fix
10+
11+ - ** The service ` container_name ` key is accepted.** ` validate() ` no longer
12+ rejects a service that sets ` container_name: ` , and the name is made
13+ resolvable to ` 127.0.0.1 ` inside the pod, exactly like ` hostname ` and network
14+ aliases already are: it joins the ` --add-host ` set so other services reach it
15+ by that name. The actual podman container keeps its internal
16+ ` {pod}-{service} ` name (used for ` podman cp ` , healthcheck polling, and
17+ diagnostics) — only name resolution is affected, matching the pod's
18+ shared network namespace.
19+
20+ ## Downstream
21+
22+ No action needed — additive and backward compatible. Documents that previously
23+ failed with ` unsupported key 'container_name' ` now emit a pod script; nothing
24+ that converted before changes.
25+
26+ ## Internals
27+
28+ - ` architecture/supported-subset.md ` merges the ` hostname ` /` container_name `
29+ note explaining both are shared-namespace-resolvable but never change the
30+ real ` --name ` .
31+ - 92 tests at 100% line coverage (enforced); ` ruff select=ALL ` , ` ty ` , and
32+ ` eof-fixer ` clean.
You can’t perform that action at this time.
0 commit comments