I recently pushed my company to move everything off of Alpine and onto Debian Slim
We had too many issues with musl that are incomprehensibly obscure and impossible to troubleshoot. Now the environment we deploy on is functionally the same to the environment our devs develop on
The v1.2.4 release might fix up some of your issues:
This release adds TCP fallback to the DNS stub resolver, fixing the longstanding inability to query large DNS records and incompatibility with recursive nameservers that don’t give partial results in truncated UDP responses. It also makes a number of other bug fixes and improvements in DNS and related functionality, including making both the modern and legacy API results differentiate between NODATA and NxDomain conditions so that the caller can handle them differently.
Not that it matters much if you’ve already migrated away to a libc distribution.
I recently pushed my company to move everything off of Alpine and onto Debian Slim
We had too many issues with musl that are incomprehensibly obscure and impossible to troubleshoot. Now the environment we deploy on is functionally the same to the environment our devs develop on
The v1.2.4 release might fix up some of your issues:
Not that it matters much if you’ve already migrated away to a libc distribution.
Isn’t this one of the primary benefits of Docker?
Development, CI, and deployment environments can and should be the same.