Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pocketblue – Fedora Atomic for mobile devices

github.com

Post reply on HN
Print view View original

51–52 of 52 posts

Re: Pocketblue – Fedora Atomic for mobile devices

#51

Post by traverseda »

nikodunk wrote: post #2

This is based on bootc (bootable containers), so note that the OS build is described in a normal Dockerfile: https://github.com/pocketblue/pocketblue/blob/main/Container... which is then run by the Github action (or locally). Very similar to how Universal Blue, Bazzite, Bluefin etc. build at https://github.com/ublue-os/bazzite (see their Containerfile), but for mobile. Has a similar mission to https://postmarketos.or…

If you're thinking about actually using it, please not it only supports redhat distros.

https://github.com/bootc-dev/bootc/issues/865

Re: Pocketblue – Fedora Atomic for mobile devices

#52

Post by arianvanp »

looperhacks wrote: post #21
arianvanp wrote: post #16

Earlier quoted context omitted.

Are we really bringing OCI to freaking OS builds? Nothing about OCI is pleasant. A list of Tarballs is the most backwards boot format I can think of. Terrible for reproducibility. Terrible for security. Boot images should be Dm-verity protected EROFS images. We should not be building new things on OCI. It's really mind-blowing to me that this is a new direction people who are supposed to be top of class OS builders a…

How is OCI terrible for reproducibility and security? They are certainly more reproducible than what we had before. I haven't heard "Works on my machine for a long time". If you're talking about reproducible builds, there aren't any hard issues either that are directly caused by OCI images - except setting the clock correctly. > Boot images should be Dm-verity protected EROFS images Maybe I'm misunderstanding you - I…

> I gather that you think the boot images are distributed as OCI image

Yes? That's literally the sales pitch on the website. Am I missing something?

Quote from https://bootc-dev.github.io/ tells me that bootc is using OCI as a delivery format for bootable images.

Transactional, in-place operating system updates using OCI/Docker container images.

Motivation The original Docker container model of using "layers" to model applications has been extremely successful. This project aims to apply the same technique for bootable host systems - using standard OCI/Docker containers as a transport and delivery format for base operating system updates

Post reply on HN