expand/awx-on-k3s
1
0
Fork 0
mirror of https://github.com/Expand-sys/awx-on-k3s synced 2025-12-15 21:42:15 +11:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: replace k3s with absolute path

Browse source
This commit is contained in:
kurokobo 2022-04-26 23:18:04 +09:00
parent 877c686f76
commit 24ad7faf6d
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
registry/README.md
View file

@ -204,13 +204,13 @@ EOF
sudo systemctl restart k3s
```
If this is successfully applied, you can check the applied configuration in the `config.registry` section of the following command. Be sure to use the `crictl` binary from k3s, otherwise you won't see your changes reflected in the `containerd` configuration used by k3s.
If this is successfully applied, you can check the applied configuration in the `config.registry` section of the following command.
```bash
sudo k3s crictl info
sudo /usr/local/bin/k3s crictl info
# With jq
sudo k3s crictl info | jq .config.registry
sudo /usr/local/bin/k3s crictl info | jq .config.registry
```
If you want Kubernetes to be able to pull images directly from this private registry, alternatively you can also manually create `imagePullSecrets` for the Pod instead of writing your credentials in `auth` in `registries.yaml`. [Another guide about rate limiting on Docker Hub](../tips/dockerhub-rate-limit.md) explains how to use `ImagePullSecrets`.