daveJun 16
In today's work-related fuckery, I'm working on some website styling. I switched my laptop to light mode, since the site uses media queries to determine if you want light or dark mode. But now I'm discovering like half the internet also does that, and the light mode styling is so weird looking to me now, it's throwing me for a loop.
Show threaddaveJun 17
more work-related fuckery: one of the bits of styling i'm updating is a oauth confirmation page. i have a separate project set up with an openid connect relying party, and spent some time setting it up to run under docker compose alongside the main site. picked two hostnames and put them in my hosts file as aliases to 127.0.0.1, and configured an nginx container to route based on the incoming hostname. confirmed all that plumbing works.

i went to finally test the damn confirmation page, and my clever 127.0.0.1 aliases aren't being returned by the dns resolver inside the compose. they are from a separate docker container, but that's not nearly as helpful as i'd like.

i have alternatives, but christ, that's like a good quarter of a day flushed.
Show threaddave
as usual, distance has brought clarity. i had overlooked the fact that i was seeing timeout errors, not lookup errors. the problem was not, in fact, dns. the problem was that the hostname resolved to 127.0.0.1, which means something different from the context of the container than it does from the host os.

i'm a little annoyed at myself for missing the obvious earlier, but at least it registered eventually, and i can move on without having that nagging "but i'm not really sure what was actually happening" feeling.
Jun 17 at 12:39pmWeb