The Docker smoke-test started the server container under the fixed name familiar-smoke. On the self-hosted runner the job shares the host Docker daemon, so a container left behind by a killed or re-run job (or a concurrent dev push + PR) collides on that name and docker run fails with exit 125 — the "container name /familiar-smoke is already in use" error seen when merging dev → main.
Fix:
Derive the container name from the commit SHA (familiar-smoke-<sha12>) via the meta step, so concurrent/parallel runs no longer share a name.
docker rm -f any stale container of that name before starting (covers re-runs of the same commit).
Thread the name through the smoke-test and cleanup steps.
No behavioural change to the actual smoke checks.
The Docker smoke-test started the server container under the fixed name `familiar-smoke`. On the self-hosted runner the job shares the host Docker daemon, so a container left behind by a killed or re-run job (or a concurrent `dev` push + PR) collides on that name and `docker run` fails with exit 125 — the "container name /familiar-smoke is already in use" error seen when merging `dev` → `main`.
**Fix:**
- Derive the container name from the commit SHA (`familiar-smoke-<sha12>`) via the `meta` step, so concurrent/parallel runs no longer share a name.
- `docker rm -f` any stale container of that name before starting (covers re-runs of the same commit).
- Thread the name through the smoke-test and cleanup steps.
No behavioural change to the actual smoke checks.
The Docker smoke-test ran the server container under the fixed name
familiar-smoke. On the self-hosted runner the job shares the host
Docker daemon, so a container left behind by a killed or re-run job
(or a concurrent dev push + PR) collides on that name and 'docker run'
fails with exit 125.
Derive the name from the commit SHA, remove any stale container of that
name before starting, and thread the name through the smoke-test and
cleanup steps.
Latte
merged commit d69c994da0 into dev2026-07-05 12:00:27 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Docker smoke-test started the server container under the fixed name
familiar-smoke. On the self-hosted runner the job shares the host Docker daemon, so a container left behind by a killed or re-run job (or a concurrentdevpush + PR) collides on that name anddocker runfails with exit 125 — the "container name /familiar-smoke is already in use" error seen when mergingdev→main.Fix:
familiar-smoke-<sha12>) via themetastep, so concurrent/parallel runs no longer share a name.docker rm -fany stale container of that name before starting (covers re-runs of the same commit).No behavioural change to the actual smoke checks.