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…
> Dockerfile nitpick: Containerfile. I mention it because people still think container==docker. I am sure the Fedora people focus on podman, as part of the Red Hat ecosystem. For a better dev experience they offer podman-bootc¹, which you will miss when using Docker. Personally I am convinced that we should steer people to podman instead of Docker. 1. https://docs.fedoraproject.org/en-US/bootc/getting-started/
Pocketblue – Fedora Atomic for mobile devices
31–40 of 52 posts
Re: Pocketblue – Fedora Atomic for mobile devices
#32Earlier quoted context omitted.
> Dockerfile nitpick: Containerfile. I mention it because people still think container==docker. I am sure the Fedora people focus on podman, as part of the Red Hat ecosystem. For a better dev experience they offer podman-bootc¹, which you will miss when using Docker. Personally I am convinced that we should steer people to podman instead of Docker. 1. https://docs.fedoraproject.org/en-US/bootc/getting-started/
Red Hat obviously wants to change people's vocabulary but "Dockerfile" is basically an industry-standard generic term by this point.
Re: Pocketblue – Fedora Atomic for mobile devices
#33Anyway, Fedora is sooo good. :D
Re: Pocketblue – Fedora Atomic for mobile devices
#34Earlier 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…
> Dm-verity protected EROFS images First time I hear about it. Playing the devils advocate: how does it improve over checksums + tarballs?
Re: Pocketblue – Fedora Atomic for mobile devices
#35How well does it work on the supported devices, including for things like calls, SMS, GPS, camera, bluetooth etc? The OnePlus 6/6T is in the "community" category of supported devices for postmarketOS and (like most devices in that category) has a laundry list of issues with hardware support that either need workarounds or just don't work at the moment. Does Pocketblue have the same limitations? Mobile Linux is a supe…
Re: Pocketblue – Fedora Atomic for mobile devices
#36how does something like this not support pinephone and librem5 from day 1?
Re: Pocketblue – Fedora Atomic for mobile devices
#37Re: Pocketblue – Fedora Atomic for mobile devices
#38Oh, Linux on mobile. My cynic take: - only works with very few phone models - battery doesn’t last long - bad UI with tiny elements. - not managing a smooth refresh rate - no apps That‘s the pattern we‘ve seen over and over again. The only approach that has worked better is to base things on AOSP.
AOSP doesn't run on a single phone on earth, not even the android emulator. Android also has it's own problems.
Re: Pocketblue – Fedora Atomic for mobile devices
#39Earlier 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…
Re: Pocketblue – Fedora Atomic for mobile devices
#40How well does it work on the supported devices, including for things like calls, SMS, GPS, camera, bluetooth etc? The OnePlus 6/6T is in the "community" category of supported devices for postmarketOS and (like most devices in that category) has a laundry list of issues with hardware support that either need workarounds or just don't work at the moment. Does Pocketblue have the same limitations? Mobile Linux is a supe…
> Mobile Linux is a super interesting but difficult area so always good to see another effort in the space, hopefully Pocketblue and postmarketOS can benefit from each other. Yea. I hope the same thing. I just wish that a defacto affordable device can finally emerge and the whole process can just be made easier and people might even base their hardware decisions on top of it. A lot of the times I find Mobile Linux un…
I assume you are refering to the Librem 5? These days the Google Pixel 3a is coming close, as multiple people report reliable phone calls. Camera is still lacking, but once libcamera add auto-focus and the device gets a driver for the focus actuator (already in the works), it's going to be just as competent with better battery-life for less than USD/EUR 100. On the more pricey side, the Fairphone 5 has a good mind share and contributor count, making it quite likely that remaining issues are being solved soon.