From 366d7db426056a85d0e6b71e43cff38c55a93d1c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=D0=9F=D1=91=D1=82=D1=80=20=D0=9F=D0=BE=D0=BB=D0=B5=D0=B6?= =?UTF-8?q?=D0=B0=D0=B5=D0=B2?= Date: Sat, 7 Feb 2026 22:49:52 +0000 Subject: [PATCH] fix formatting --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 39ac17c..ec175bc 100644 --- a/README.md +++ b/README.md @@ -9,8 +9,8 @@ wait for docker operations to complete and those are async. Podman does not seem # Kernel pre-requisites For this to work you need to make sure that you have the following enabled in the kernel -- CONFIG_NF_TABLES_INET (needs CONFIG_IPv6) -- CONFIG_NFT_FIB_INET (needs CONFIG_NFT_FIB_IPV4 and CONFIG_NFT_FIB_IPV6) +- `CONFIG_NF_TABLES_INET` (needs `CONFIG_IPv6`) +- `CONFIG_NFT_FIB_INET` (needs `CONFIG_NFT_FIB_IPV4` and `CONFIG_NFT_FIB_IPV6`) and your host kernel is a decently new one. So if you are still on the time-proven debian from 2002 with kernel 2.6.* it might be a good idea to upgrade. Tested on 6.18.7. YMMV @@ -39,8 +39,8 @@ container: Using Gitea's Helm chart for the runner https://gitea.com/gitea/helm-actions/ -[!NOTE] -You need the >v0.0.2 release which, at the time of writing this, does not exist. So use the tarball URL as your helm chart directly. +> [!NOTE] +> You need the >v0.0.2 release which, at the time of writing this, does not exist. So use the tarball URL as your helm chart directly. `values.yaml`: ```yaml @@ -66,5 +66,5 @@ existingSecretKey: giteaRootURL: ``` -[!NOTE] -You either need to mount `/var/lib/containers` as shown or you need `fuse` working. The `fuse` option is not tested \ No newline at end of file +> [!NOTE] +> You either need to mount `/var/lib/containers` as shown or you need `fuse` working. The `fuse` option is not tested \ No newline at end of file