Skip to content

Update private-registry.md #481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 1, 2025
+1 −1
Merged

Update private-registry.md #481

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
35462f5
Update private-registry.md
farazkhawaja Sep 29, 2025
9517a60
Update docs/installation/private-registry.md
farazkhawaja Sep 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/installation/private-registry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,7 +255,7 @@ In order for the registry changes to take effect, you need to restart K3s on eac
When Kubernetes experiences problems pulling an image, the error displayed by the kubelet may only reflect the terminal error returned
by the pull attempt made against the default endpoint, making it appear that the configured endpoints are not being used.

Check the containerd log on the node at `/var/lib/rancher/k3s/agent/containerd/containerd.log` for detailed information on the root cause of the failure.
Check the containerd log on the node at `/var/lib/rancher/k3s/agent/containerd/containerd.log` for detailed information on the root cause of the failure. Note that you must look at the logs on the node where the pod was scheduled. You can check which node your pod was scheduled to by issuing `kubectl get pod -o wide -n NAMESPACE POD` and checking the the NODE column.

## Adding Images to the Private Registry

Expand Down
Loading