frosty

joined 2 years ago
[–] frosty@pawb.social 4 points 2 years ago

Still using it as a self-hosted PWA over here. I've even made a script to fetch a version from git, cross compile it for my Pi and ship it over. Keep up the good work! :)

[–] frosty@pawb.social 17 points 2 years ago* (last edited 2 years ago)

…only mildly infuriating?!

At least this restaurant due is showing their own ass.

[–] frosty@pawb.social 4 points 2 years ago (1 children)

When I first encountered the photo, I thought I was looking at the latest superhighway in China. Then I saw the signs in English at the bottom right. 😞

[–] frosty@pawb.social 1 points 2 years ago

ETA - Since rebuilding my PWA host, I've had no issues with running the corepack inside of buildx. Dual-stack is enabled, so it's a mystery what happened! Maybe the folks hosting corepack fixed an issue with their hosting.

[–] frosty@pawb.social 20 points 2 years ago

I'm sorry for your loss, mate. It's hard. :(

[–] frosty@pawb.social 2 points 2 years ago (3 children)

Growing up with Sicilian grandparents, we were often served “braciolini”, mini-braciole on a skewer with a meal sometimes. Ours were always steak and breadcrumbs. This looks interesting!

[–] frosty@pawb.social 2 points 2 years ago

Fingers crossed!

[–] frosty@pawb.social 3 points 2 years ago

Weirder yet, posting this now didn’t require anything, neither did it when I posted here a week ago.

[–] frosty@pawb.social 1 points 2 years ago

It was wild out here in Marlboro. I tried to get out for a walk last night before the rain came. Three minutes after stepping outside, a thunderbolt struck extremely close by in the neighborhood, and I NOPEd right back indoors.

[–] frosty@pawb.social 1 points 2 years ago

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.)

[–] frosty@pawb.social 1 points 2 years ago* (last edited 2 years ago)

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!

[–] frosty@pawb.social 1 points 2 years ago (1 children)

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. 😅

view more: ‹ prev next ›