Hiddenden/familiar
5
0 Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
41 Commits 2 Branches 0 Tags
4acf6836628157f829f864b6074341c5763a2830
Commit Graph
2 Commits
Author SHA1 Message Date
Latte 4acf683662 fix(ci): smoke-test the image over its bridge IP, not a published host port
CI / lint (pull_request) Successful in 56s
Details
docker / lint (pull_request) Successful in 58s
Details
docker / test (pull_request) Successful in 1m7s
Details
CI / test (pull_request) Successful in 1m8s
Details
CI / publish (pull_request) Has been skipped
Details
docker / docker (pull_request) Has been cancelled
Details 
Self-hosted runners can execute job steps as a sibling container sharing
the host's Docker socket, so -p 18080:8080 publishes on the runner host
rather than inside the step's own container — 127.0.0.1 never reaches it
(curl exit 7). Container-to-container traffic over the bridge network
always works, so resolve the smoke container's own IP and probe that.
 2026-07-05 13:31:49 +02:00
Latte eb2922f63c ci(docker): build, smoke-test, and publish the remote-HTTP image 
New .gitea/workflows/docker.yml (alongside the untouched ci.yml wheel publish).
Runs lint + test, then builds the image and smoke-tests it — non-root uid,
/healthz 200, MCP 401 without a token and 200 with a valid bearer. On a merge to
main/dev it pushes to git.hiddenden.cafe/hiddenden/familiar (main -> :latest +
:main, dev -> :dev, plus :sha-<12>) via the existing REGISTRY_TOKEN, then does a
scoped cleanup. The two workflows are independent and don't interfere.
 2026-07-04 19:26:17 +02:00