Update private-registry.md #438
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I added some clarifying information on _which_ node's containerd logs to check, as this is a frequently requested item from the maintainers on the Issues page of this repo. Signed-off-by: Sonny Rajagopalan <[email protected]>
dereknola
approved these changes
Jun 26, 2025
farazkhawaja
reviewed
Aug 4, 2025
| @@ -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. In case you have a multi-node set up (common), you can check which node your image was attempted deployment at by issuing `kubectl describe pod <pod-name> and getting the name of the node. You will have to check the containerd log on _that_ node. | |||
There was a problem hiding this comment.
Do we need to give out exact command ie ; k describe pod | grep "Node:"
There was a problem hiding this comment.
kubectl get pod -o wide -n NAMESPACE POD would be a better suggestion, as the wide output includes the node.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added some clarifying information on which node's containerd logs to check, as this is a frequently requested item from the maintainers on the Issues page of this repo.