Excellent read, I loved it.

Incidentally, the image seems to be the one the resort uses on their website! https://oanresort.wixsite.com/chuuk

thanks, and yea, it should be solved easily by passing the img to google lens, the website is the first result, but I found a fun opportunity to solve it in different way

nah we'll verb anything

Fun easter egg: the barcode on the cover (the one on the left at least) is for the book's ISBN.

Can you imagine how annoying it would be for checkout workers to have a giant barcode with a different product on the front of a book!

https://www.nola.com/news/hurricane/weather-satellite-goes-1... explains a bit more what this is, and what this means.

> The main NOAA satellite for tracking Atlantic, Gulf Coast hurricanes is out until further notice

> GOES-19 is the main instrument used to identify tropical waves as they strengthen and move over the Atlantic, Caribbean and Gulf of Mexico, providing real-time tracking for forecasting.

Already been done https://grit-scm.com/

I fell down a YouTube hole and watched all of these Derail Valley playthroughs: https://youtu.be/JSONttyEJ4o

Highly recommend if you like having something interesting on in the background.

Relatedly, I vibecoded this a few days ago for fun: https://imjasonh.github.io/kubescheduler-the-game/

It was fun.

This game has got my name written all over it

You absolutely can just build things and put them on base images without building or pulling the base image at any point. This is a central feature of ko, a simple container build tool for most Go applications: https://ko.build

(I am a maintainer)

I love seeing folks learn that container images are just fancy tar files and JSON and are therefore buildable by normal tools.

Along my own journey of demystification I made a few toy container image registries over the years that generated and served container images from nothing but the URL itself:

https://ko.kontain.me builds a go application on demand and serves it atop a minimal base image

https://apko.kontain.me builds a base image containing packages listed in the URL, again on demand.

The latest addition, https://git.kontain.me serves an image with the specified git repo already checked out in the image.

None of these should be used for anything serious but they were fun to make and play with. :)

random.kontain.me has been uncharacteristically useful in debugging image caching scenarios.

I don't know any scenario where I'd need any of that, but I love such things regardless.

About git.kontain.me - what if I'd like to setup my own copy of such a service and would like it to work with a non-public git repo, how to pass credentials? Since you support only cloning over https (btw, why not over ssh as well?) - one could use an URL of format user:pass@host:port/path/to/repo, would that work?

Unfortunately due to the limitations of a valid image ref you can't include creds like that.

You can fork the registry and include your own creds in the backend when it pulls the repo though.

I sometimes wonder why there aren't more bespoke container tools (like yours). Would people be willing to pay for stuff like what you have built, if someone took the time to "productionize" it? Or is there no market?

AFAIK people only begrudgingly pay for Docker and it does way waaay more.

I have yet to receive any commercial interest in any of these tools :)

What's NASA :)

~Well, if you asked a randomly-chosen person (technical or non-technical) they would probably say NASA is "the organization that does the space things" — it's pretty well-known~

~On the other hand, BPF means different things in different domains, and isn't ubiquitous in the same way~

Edit: I should have written it out, that's on me :-)