actions/runner-container-hooks
1
0
Fork 0
mirror of https://github.com/actions/runner-container-hooks.git synced 2025-12-16 17:56:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update 0034-build-docker-with-kaniko.md

Browse Source
This commit is contained in:
Ferenc Hammerl
2023-01-04 12:18:51 +01:00
committed by GitHub
parent a62b81fc95
commit 0c38d44dbd
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/adrs/0034-build-docker-with-kaniko.md
View File

@@ -29,7 +29,9 @@ EITHER
- `ACTIONS_RUNNER_CONTAINER_HOOKS_REGISTRY_NODE_PORT` # NodePort - the K8S job will pull the image from here - `ACTIONS_RUNNER_CONTAINER_HOOKS_REGISTRY_NODE_PORT` # NodePort - the K8S job will pull the image from here
- The hooks then build up a URI like `localhost:${registryNodePort()}/${generated-random-string-handle-image}` for the k8s job to pull from - The hooks then build up a URI like `localhost:${registryNodePort()}/${generated-random-string-handle-image}` for the k8s job to pull from
- `localhost` is the current limitation enforcing the existence of a docker registry exposed through the `nodePort` of a k8s service - `localhost` is the current limitation enforcing the existence of a docker registry exposed through the `nodePort` of a k8s service
OR OR
- Define a remote docker registry (dockerhub, ghcr) and its secrets (WIP) - Define a remote docker registry (dockerhub, ghcr) and its secrets (WIP)
To execute a container-action, we run a k8s job by loading the image from the specified registry To execute a container-action, we run a k8s job by loading the image from the specified registry