maddo/maddoscientisto-net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Add Docker CLI bootstrap and update README with DOCKER_HOST instructions
Some checks failed
Publish Container / publish (push) Failing after 1m0s
Details

Browse source
This commit is contained in:
MaddoScientisto 2026-03-14 17:48:36 +01:00
commit 1f29b94491
2 changed files with 45 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -41,6 +41,7 @@ Set these Forgejo Actions variables:
- `FORGEJO_REGISTRY` (example: `forgejo.example.com`)
- `IMAGE_NAMESPACE` (example: `maddo`)
- `IMAGE_NAME` (example: `maddoscientisto-web`)
- Optional: `DOCKER_HOST` (example: `tcp://forgejo-docker-in-docker:2375`)
Set these Forgejo Actions secrets:
@ -53,3 +54,12 @@ The workflow in `.forgejo/workflows/publish-container.yml` runs on pushes to `ma
- `${FORGEJO_REGISTRY}/${IMAGE_NAMESPACE}/${IMAGE_NAME}:latest`
- `${FORGEJO_REGISTRY}/${IMAGE_NAMESPACE}/${IMAGE_NAME}:sha-<12-char-commit>`
## Forgejo runner notes (Docker-in-Docker)
If the runner image does not contain the `docker` binary, the workflow bootstraps a Docker CLI in user space before login/build/push.
For dind-based runners, ensure the job can reach your daemon over `DOCKER_HOST`.
With your compose topology, the default `tcp://forgejo-docker-in-docker:2375` should work.
If you still get connection failures after the CLI bootstrap step, set a repo variable named `DOCKER_HOST` to the correct daemon endpoint for your runner network.