novox/hq 04-ISSUES/025. Every image reference in every example module was sixty-four zeros — eighteen of them across five modules. Each parsed, resolved, and composed into a declaration a host accepts, and none could ever have started: the machine reaches `docker pull` and stops. That is why those modules were written and not running, and no check saw it because every check passed. The host validates the shape of a reference and nothing more, which is correct: verifying a digest exists means reaching a registry, and that is the one thing a host must never have to do. So the last place that could catch this is the wrong place to try. The guard therefore sits where a declaration is composed, not where a manifest is parsed. A file in a repository is allowed to await a pin — the design already says the manifest in a repository names artifacts while the manifest the mesh holds names digests, and the bundle works exactly that way. What must never happen is a placeholder reaching a machine, and composing is the last moment before one does. Twelve third-party images resolved to real digests without pulling anything, which is also the mechanism the open issue needs. Two discoveries came free: mailu publishes to ghcr rather than Docker Hub, so seven references named repositories that do not exist at all; and it renamed roundcube to webmail, so that one would have failed even with the right registry. What stays a placeholder is the mesh's own provisioner images, which genuinely have no digest until built and pushed — the bundle's problem, legitimately unresolved here. The stand-in consumer now stands in with a real image rather than an invented one.
42 lines
1.7 KiB
JSON
42 lines
1.7 KiB
JSON
{
|
|
"module": "keycloak",
|
|
"version": "1",
|
|
|
|
"requires": ["postgres-database"],
|
|
"contributes": {
|
|
"postgres-database": {"name": "keycloak"}
|
|
},
|
|
"binds": {"postgres-database": "/var/lib/keycloak/database.json"},
|
|
"secrets": {"postgres-database": "/var/lib/keycloak/database.secret"},
|
|
|
|
"capabilities": ["container-runtime"],
|
|
|
|
"listens": [
|
|
{"port": 8080, "protocol": "tcp", "from": "mesh",
|
|
"why": "anything the mesh runs that authenticates a person"}
|
|
],
|
|
|
|
"own-secrets": {"admin": "/var/lib/keycloak/admin.secret"},
|
|
|
|
"resources": [
|
|
{"id": "state", "type": "directory", "path": "/var/lib/keycloak", "mode": "0700"},
|
|
|
|
{"id": "admin-env", "type": "file", "path": "/var/lib/keycloak/admin.env", "mode": "0600",
|
|
"content": "KEYCLOAK_ADMIN=admin\nKEYCLOAK_ADMIN_PASSWORD=${secret:admin}\n"},
|
|
|
|
{"id": "database-env", "type": "file", "path": "/var/lib/keycloak/database.env", "mode": "0600",
|
|
"content": "KC_DB_URL=jdbc:postgresql://${bound:postgres-database:at}:${bound:postgres-database:port}/keycloak\nKC_DB_USERNAME=${bound:postgres-database:as}\nKC_DB_PASSWORD=${secret:postgres-database}\n"},
|
|
|
|
{"id": "net", "type": "network", "name": "keycloak"},
|
|
|
|
{"id": "server", "type": "container", "name": "keycloak",
|
|
"image": "quay.io/keycloak/keycloak@sha256:ecd43971114b0c764f8a3288dddab73f98cb473daccc4feaffe4dc14adeaf866",
|
|
"network": "keycloak",
|
|
"args": ["start-dev"],
|
|
"env": {"KC_DB": "postgres", "KC_HTTP_ENABLED": "true", "KC_HEALTH_ENABLED": "true"},
|
|
"env-file": ["/var/lib/keycloak/admin.env", "/var/lib/keycloak/database.env"],
|
|
"ports": ["8080:8080"],
|
|
"restart-on": ["admin-env", "database-env"]}
|
|
]
|
|
}
|