No description
- Dockerfile 53.9%
- Shell 46.1%
| forgejo/ubuntu | ||
| tools | ||
| build.sh | ||
| README.md | ||
docker-images
A single repo for all my container images (Forgejo CI runners, test-stack helpers, etc.) and a build script (build.sh) that can build & push any subset of them.
Repository Layout
.
├── build.sh # one-stop build & push tool
├── forgejo/
│ ├── ubuntu/
│ │ ├── 22.04/ -> ubuntu-2204
│ │ └── 24.04/ -> ubuntu-2404
│ └── alpine/
│ └── 3.19/ -> alpine-319
└── tests/
Add a new image by adding another folder that contains a Dockerfile.
Tag-naming rule
- Drop the top-level folder (
forgejoortests). - Replace every remaining “/” with “-”.
- Strip dots from the version segment.
| Path example | Resulting tag |
|---|---|
forgejo/ubuntu/24.04 |
ubuntu-2404 |
tests/postgres/16 |
postgres-16 |
forgejo/alpine/3.19 |
alpine-319 |
The final image name is
<REGISTRY>:<tag> — the registry is configured at the top of build.sh.
Quick start
# 0) One-time login (uses registry host part)
docker login git.berger-em.net
# 1) Build & push every Dockerfile in the repo
./build.sh
Build specific images only
# single folder
./build.sh forgejo/ubuntu/24.04
# multiple
./build.sh tests/postgres/16 forgejo/alpine/3.19
You can also point directly at an individual Dockerfile.