docs: manifest erratum, Anubis runs as anubis@keel.service on ::1 #33

Merged
marcos-mendez merged 2 commits from docs/manifest-anubis-erratum into main 2026-10-01 14:38:48 -03:00
marcos-mendez commented 2026-10-01 01:31:23 -03:00 (Migrated from github.com)

Erratum to docs/manifest-v1.md, worked example of Keel Web, found by step 6 of decision 0041 (Keel-Linux/common#21):

  • the Anubis overlay's unit is anubis@keel.service, an instance of the template anubis@.service that step 5's anubis package ships (rule 5 finds an instance by its template), not anubis.service;
  • its port declares address: "::1", the one family it binds, and the resolved port table reads loopback, IPv6.

keel-overlay-anubis in common#21 already ships the manifest this way; keel manifest validate accepts it on the Core image.

Erratum to docs/manifest-v1.md, worked example of Keel Web, found by step 6 of decision 0041 (Keel-Linux/common#21): - the Anubis overlay's unit is `anubis@keel.service`, an instance of the template `anubis@.service` that step 5's anubis package ships (rule 5 finds an instance by its template), not `anubis.service`; - its port declares `address: "::1"`, the one family it binds, and the resolved port table reads `loopback, IPv6`. keel-overlay-anubis in common#21 already ships the manifest this way; `keel manifest validate` accepts it on the Core image.
Sign in to join this conversation.
No description provided.