Skip to content
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.

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

Improvement for k8s.io/docs/tasks/debug-application-cluster/debug-running-pod/ #31930

Closed
guettli opened this issue Feb 26, 2022 · 2 comments · Fixed by #31989
Closed

Improvement for k8s.io/docs/tasks/debug-application-cluster/debug-running-pod/ #31930

guettli opened this issue Feb 26, 2022 · 2 comments · Fixed by #31989
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@guettli
Copy link
Contributor

guettli commented Feb 26, 2022

The command nslookup of busybox is broken since several month.

The above page uses the image busybox.

This drove me crazy during the last hours.

Here the example of my KinD cluster:

root@kind-control-plane:/# kubectl run -it --rm --restart=Never busybox --image=busybox sh

/ # nslookup kubernetes.default
Server:		10.96.0.10
Address:	10.96.0.10:53

** server can't find kubernetes.default: NXDOMAIN

busybox:1.28 works:

root@kind-control-plane:/# kubectl run -it --rm --restart=Never busybox --image=busybox:1.28 sh

/ # nslookup kubernetes.default
Server:    10.96.0.10
Address 1: 10.96.0.10 kube-dns.kube-system.svc.cluster.local

Name:      kubernetes.default
Address 1: 10.96.0.1 kubernetes.default.svc.cluster.local

I very big thank you for the people in #kubernetes-users for pointing me into the right direction.

Related issue: docker-library/busybox#48 (closed because upstream needs to solve this)


It would be good if the above page would use busybox:1.28 instead of busybox.

I can do the change (PR), but first I want to know what you think. Maybe there is a better solution. Maybe there is a better base-image than busybox.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 26, 2022
@tengqm
Copy link
Contributor

tengqm commented Feb 27, 2022

/triage accepted
/kind bug
PRs are welcomed.

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. kind/bug Categorizes issue or PR as related to a bug. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 27, 2022
@guettli
Copy link
Contributor Author

guettli commented Mar 1, 2022

I created a PR: #31989

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants