From 0c38d44dbd217f9cc62234cee9d86ec5b4dd4095 Mon Sep 17 00:00:00 2001
From: Ferenc Hammerl <31069338+fhammerl@users.noreply.github.com>
Date: Wed, 4 Jan 2023 12:18:51 +0100
Subject: [PATCH] Update 0034-build-docker-with-kaniko.md

---
 docs/adrs/0034-build-docker-with-kaniko.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/adrs/0034-build-docker-with-kaniko.md b/docs/adrs/0034-build-docker-with-kaniko.md
index 64fd4e0..5cd7cad 100644
--- a/docs/adrs/0034-build-docker-with-kaniko.md
+++ b/docs/adrs/0034-build-docker-with-kaniko.md
@@ -29,7 +29,9 @@ EITHER
     - `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
     - `localhost` is the current limitation enforcing the existence of a docker registry exposed through the `nodePort` of a k8s service
+
 OR
+
 - 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