*BUSYBOX vs BUSYBOX:1.28* Something I had noticed when doing the course but whi . . .

Kubernetes
#1

OE:
BUSYBOX vs BUSYBOX:1.28

Something I had noticed when doing the course but which I think wasn’t explicitly mentioned (I’m not sure), is why you use busybox:1.28 instead of the latest version of busybox when troubleshooting and using tools like nslookup

So I asked myself, why? After a little digging, I ran into this - https://github.com/docker-library/busybox/issues/48

So it looks like this is due to a upstream change in nslookup in busybox. So remember to stick to busybox:1.28

#2

Michael Cuffaro:
yeah I believe it is mentioned in one of the lab solutions, but it’s great to have a reminder of that here!

#3

J B P:
Try netcommand nc in busybody latest works for me

#4

J B P:
netconnect