Differences

This shows you the differences between two versions of the page.

--- k8s:distributions:rke2 [2023/10/24 13:35] – admin
+++ k8s:distributions:rke2 [2023/11/11 18:21] (current) – admin
@@ Line 56: / Line 56: @@
 protect-kernel-defaults: false
 ```
+Create a `/etc/rancher/rke2/registries.yaml` for using a local docker.io mirrir which will look something like:
+```yaml
+mirrors:
+  docker.io:
+    endpoint:
+      - "http://10.6.16.58:5000"
+```
 ### Server
@@ Line 81: / Line 89: @@
 For flatcar-linux we can follow the advice on the sig-storage-local-static-provisioner website: Mount formatted block storage on `/mnt/local-disks/<UUID>`. The UUID will be used to make sure mixing block devices will fail and not expose data to the wrong host.
-. Create a block device for an acdh-clusterX node in vCenter. Note that the size of the block device should be a little larger than the desired even number if GiB (example: for a 20 GiB volume create a 21 GiB disk) as there is a difference in how disk size is calculated
+* Create a block device for an acdh-clusterX node in vCenter. Note that the size of the block device should be a little larger than the desired even number if GiB (example: for a 20 GiB volume create a 21 GiB disk) as there is a difference in how disk size is calculated
-. Format the volume on the respective flatcar node. Use ext4 or xfs depending on the needs of the service (for example elasticsearch/opensearch recommeds ext4)
+* Format the volume on the respective flatcar node. Use ext4 or xfs depending on the needs of the service (for example elasticsearch/opensearch recommeds ext4)
 ```bash
-        sudo mkfs.ext4 /dev/sdd
+sudo mkfs.ext4 /dev/sdd
 ```
-. reserved blocks for root are not very useful in kubernetes so set them to 0
+* reserved blocks for root are not very useful in kubernetes so set them to 0
 ```bash
 sudo tune2fs -r 0 /dev/disk/by-uuid/<UUID>
 ```
-. Get the UUID. It is part of the output of mkfs.ext4. It is also for example available using using `ls -l /dev/disk/by-uuid/*`
+* Get the UUID. It is part of the output of `mkfs.ext4` above. It is also for example available using using `ls -l /dev/disk/by-uuid/*`
-. Create a UUID directory in /mnt/local-disks/
+* Create a mount unit to mount the filesystem. The filename needs to match the mount point and is encoded.
-. Create a mount unit to mount the filesystem. The filename needs to match the mount point and is encoded.
+  This will automatically create a `<UUID>` directory in `/mnt/local-disks/`
-  ```bash
+```bash
 sudo cp /etc/systemd/system/var-lib-rancher.mount "/etc/systemd/system/$(systemd-escape --path /mnt/local-disks/<UUID>).mount"
 sudo vi /etc/systemd/system/"$(systemd-escape --path /mnt/local-disks/<UUID>).mount"
@@ Line 127: / Line 135: @@
 [Here](https://update.rke2.io/v1-release/channels) you can see what version corresponds to stable at the moment.
 Kubernetes major versions are also channels. The channel latest refers to the very latest releases of K8s available.
+## Troubleshooting
+### Using command line tools to manually delete container images images
+```bash
+sudo -s
+# as root
+export PATH=$PATH:/var/lib/rancher/rke2/bin
+export CONTAINERD_ADDRESS=/run/k3s/containerd/containerd.sock
+ctr -n k8s.io i rm $(ctr -n k8s.io i ls -q | grep <image name to delete, regex>)
+# or
+export CONTAINER_RUNTIME_ENDPOINT=unix:///run/k3s/containerd/containerd.sock
+crictl images
+crictl rmi <image name to delete>
+```