Cannot resolve another docker container hostname

[wader]

Cannot resolve another docker container hostname

[wader]

Hi, looking at the ffmpeg version output it looks like the binary is from https://johnvansickle.com/ffmpeg/? it's a similar project to this. Maybe move it here?

But that said i've had DNS issue with alpine myself when the DNS response was very large (it does not support DNS over TCP). Maybe try ffmepg -v trace for more verbose output, also maybe see if netcat or some other non-network debug tool can resolve. Also a bit suspicious that this seems to be static binary build on debian (glibc) but is running in alpine (musl libc). Could be NSS issues etc? you could try a binary from this project which is build statically with musl.

[SuperCuber]

Ah I see. I assumed it was using this project, my bad :)

Netcat resolves the hostname just fine. Very strange, and based on drills output it doesn't look like the dns response is too large - just one record. I can't find an issue board for johnvansickle's project and I solved my own issue so I don't think I'm going to keep debugging this. TY for the swift response though :D

[wader]

No problem, what was the issue or solved it some other way?

[SuperCuber]

I switched to tnk4on/yt-dlp:alpine-pip instead of tnk4on/yt-dlp:alpine-static, which uses a different ffmpeg with

  built with gcc 10.3.1 (Alpine 10.3.1_git20211027) 20211027

[wader]

Ok, that seems to use ffmpeg from alpine. I suspect some kind of glibc NSS issue with alpine-static, static glibc is messy.

[mathieu-aubin]

Try installing 'nscd' to fix dns resolution issues for binaries compiled using static glibc. Its probably installed in the container already, in the one that works fine.