You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! First of all, thank you for implementation of HA version of node-cache :)
But what is the main reason of usage alpine image as a base? It has some unresolve issues that affected DNS resolving and community recommends to use debian-based image to avoid these problems.
Do you have any problems with alpine-based image?
The text was updated successfully, but these errors were encountered:
Hi @rbakhtaraev , that's a great question. Indeed Musl can be less configurable than glibc for DNS - which is a problem we looked at while investigating DNS timeouts a couple years ago. On the other hand, coredns is written in Go and Go can be quite opinionated on DNS too. Are there specific issues you are seeing with coredns-nodecache where a glibc backed image would help?
Right now we haven't any problem, because it isn't deployed yet. But most of papers about K8S and DNS says that better glibc to use and i decided to ask you for sure.
I'll trying to use alpine as a base. Thank you for quick reply!
Hello! First of all, thank you for implementation of HA version of node-cache :)
But what is the main reason of usage alpine image as a base? It has some unresolve issues that affected DNS resolving and community recommends to use debian-based image to avoid these problems.
Do you have any problems with alpine-based image?
The text was updated successfully, but these errors were encountered: