-
Notifications
You must be signed in to change notification settings - Fork 663
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
Problem with exercise "Multi-container Pod – init container" #26
Comments
Got the same issue. Switched version of busybox to 1.28.4 in the YAML file and all working. |
lukaso
added a commit
to lukaso/TheK8sBook
that referenced
this issue
Jan 8, 2023
nigelpoulton
added a commit
that referenced
this issue
Jan 9, 2023
Fix "Multi-container Pod – init container" #26
I merged you PR pinning the 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the
initpod.yml
file you are using for the init containerinit-ctr
the imagebusybox
. However, the command to check that the servicek8sbook
is up, does not work. Apparently, it is related to the version of the image. You can see in this issue that there have been some unsolved problems for recent versions okbusybox
regardingnslookup
that have not been addressed yet. The recommendation in the issue from other users (and what actually worked out for me) is to pin the version to be<=1.28.4
. Also, there are some users that suggest using a different image for the same purposes with Kubernetes.The text was updated successfully, but these errors were encountered: