diff options
| author | Paul Buetow <paul@buetow.org> | 2025-07-31 15:03:04 +0300 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2025-07-31 15:03:04 +0300 |
| commit | e3df76d0532147462e1f873489798ec882bb56a4 (patch) | |
| tree | 92a5dcf1d8980f10d13446efe13a799a0fc98b77 | |
| parent | 04cbbb338462968f63ca69c95223dea28252168d (diff) | |
update readme
| -rw-r--r-- | f3s/registry/README.md | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/f3s/registry/README.md b/f3s/registry/README.md index 3049532..591f244 100644 --- a/f3s/registry/README.md +++ b/f3s/registry/README.md @@ -35,3 +35,25 @@ This document describes how to push Docker images to the private registry deploy ## Communication The Docker registry is exposed via a static NodePort (`30001`) and uses plain HTTP. It is not configured for TLS. + + + First, run this command to create or update the configuration file. This command will overwrite the file if it exists. + + 1 sudo bash -c 'echo "{ \\"insecure-registries\\": [\\"r0.lan.buetow.org:30001\\",\\"r1.lan.buetow.org:30001\\",\\"r2.lan.buetow.org:30001\\"] }" > /etc/docker/daemon.json' + + After running that command, you need to restart your Docker daemon for the changes to take effect. + + 1 sudo systemctl restart docker + + +And afterwards I could push the anky-sync-server image. + +## K3s Configuration + +To use the private registry from within the k3s cluster, you need to configure each k3s node to trust the insecure registry. This is done by creating a `registries.yaml` file in `/etc/rancher/k3s/` on each node. + +The following command will create the file and restart the k3s service: + +```bash +ssh root@<node> "echo -e 'mirrors:\n "registry.lan.buetow.org:30001":\n endpoint:\n - "http://localhost:30001"' > /etc/rancher/k3s/registries.yaml && systemctl restart k3s" +``` |
