OpenWRT
/
docker
mirror of https://github.com/openwrt/docker.git
1
0
Fork 0
Code Issues Releases Wiki Activity

README: document GitHub Actions registry secrets configuration

pull/204/head
Josef Schlehofer 2026-06-24 23:17:04 +02:00
parent dec0e57865
commit 3a05395430
No known key found for this signature in database
GPG Key ID: 942FF3271E2AC7DB
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -132,6 +132,25 @@ access. Once closed the container is removed.
* `malta/be` or `mips_24kc`
* `mvebu/cortexa9` or `arm_cortex-a9_vfpv3-d16`
## GitHub Actions CI & Registries
The GitHub Actions workflow `.github/workflows/containers.yml` automatically builds and pushes the containers to the registries. If you fork this repository, you can also push to your own registry accounts.
### GitHub Container Registry (GHCR)
By default, the workflow will push containers to `ghcr.io/${{ github.repository_owner }}/<image>`. This works automatically out of the box using GitHub's built-in `GITHUB_TOKEN` and does not require any additional setup.
### Docker Hub & Quay.io
To push to your own Docker Hub or Quay.io registries, you need to configure the following secrets under your repository's **Settings -> Secrets and variables -> Actions**:
* **Docker Hub (docker.io)**:
* `DOCKER_USER` - Your Docker Hub username.
* `DOCKER_TOKEN` - Your Docker Hub Personal Access Token.
* **Quay.io (quay.io)**:
* `QUAY_USER` - Your Quay.io username.
* `QUAY_TOKEN` - Your Quay.io OAuth Token / Password.
If these secrets are not configured, the workflow will automatically skip logging in and pushing to these registries without failing the build.
## Build Your Own
If you wan to create your own container you can use the `Dockerfile`. You can set the following build arguments: