Should have been an AITA and not an AMA.

Yes, in theatres with my mother, since Sears (where she worked) had an exclusive screening at the cinema in the neighboring mall.

My partner and I were there in May, and can confirm for an east coast US city dweller the prices in Oslo and Bergen were very reasonable.

(Denmark was more expensive!)

We took the Vy train from Oslo to Bergen, and it was beautiful. We also stopped about halfway in a ski community called Finse. Even in May it was snow covered.

Not sure why this reminds me of Monadnock, since that’s in NH. I’m a lifelong Bay Stater and don’t recognize this view. 😅

I do run IPv6, but not exclusively!

Tacking “strace” onto the front of the docker build command gives me a lot of nice output before step 1, but at the crucial step 3, there’s nothing. However, I decided to temporarily disable IPv6 processing on the device, and lo and behold, it carries on without a problem.

That means either my IPv6 tunnelbroker or some of BuildKit’s services are having issues handling IPv6 traffic. (I was gonna say it was corepack, but that’s run even with BuildKit turned off.) Now to find a way to get the build to work with IPv6, but that’s my homework now.

Thanks for the tip!

Home

I prefer Queen of Kings to Pretty Devil, but it’ll grow on me! And her career is only getting boosted by her Eurovision appearance. :D

QoK was in my top 5! I want to say it was #2 or #3.

By the way, since I did the one build with IPv6 disabled, I’ve since re-enabled it, and subsequent builds seem to accept that corepack is cached and haven’t had further issues. Should it come up again, I’m going to have tcpdump running in the background just to see whether there is some host that the build process is trying to lookup that is returning bogus AAAA responses. (More often than not IPv6 problems stem from improper configuration either on the client or server side.)