mirror of
https://github.com/kata-containers/kata-containers.git
synced 2026-07-10 15:56:47 +00:00
443a999323
Parameterize the remaining Docker Hub base images so CI can pull them from
the ghcr.io mirror without hardcoding it in the Dockerfiles:
* kata-deploy/{Dockerfile,Dockerfile.components}, kata-monitor, kata-debug,
kubectl, kata-webhook, dracut and the build-kata-deploy (dockerbuild)
helper now use ARG IMAGE_REGISTRY=docker.io + FROM ${IMAGE_REGISTRY}/...
* their build scripts pass --build-arg IMAGE_REGISTRY only when the env var
is set (default behavior unchanged for local builds)
* the build-kata-deploy-components CI jobs and publish-kata-images set
IMAGE_REGISTRY=ghcr.io/kata-containers
The gcr.io/distroless runtime bases are intentionally left untouched.
Authored-by: Cursor <cursor@cursor.com>
Signed-off-by: Fabiano Fidêncio <ffidencio@nvidia.com>
kata-debug
kata-debug is a tool that is used as part of the Kata Containers CI to gather
information from the node, in order to help debugging issues with Kata
Containers.
As one can imagine, this can be expanded and used outside of the CI context, and any contribution back to the script is very much welcome.
The resulting container is stored at the Kata Containers quay.io
space and can
be used as shown below:
kubectl debug $NODE_NAME -it --image=quay.io/kata-containers/kata-debug:latest
Building and publishing
The project can be built and publish by calling the following command from the Kata Containers top directory:
make build-and-publish-kata-debug
Users can specify the following environment variables to the build:
KATA_DEBUG_REGISTRY- The container registry to be used default:quay.io/kata-containers/kata-debug
KATA_DEBUG_TAG- A tag to the be used for the image default:$(git rev-parse HEAD)-$(uname -a)