Hi fellow Pi peeps, this is my first post since creating my account five years ago without needing help, so I hope I have made this post in the correct section of the board.
Just to scratch the surface, I have been playing around with CM4s for quite a while now, I own three with differing specs (2G/32G, 1G/8G, 8G/8G), but now I have made a start of looking to create a custom, stripped-down, "deployment image" with a lower install and RAM footprint than Pi OS, with the consensus that the OS runs from a read-only root, and with updates done whilst the image is "offline", by ways of through another RPi device over USB (with the bootloader switch on), similar to how the Windows' DISM utility can service both online and offline images.
What I have attempted to do prior to making this post, is to use debootstrap, apt(-get) and dpkg on the destination volume (with apt -o Dir=${PWD}) to strip out the parts (including apt and dpkg themselves from the image) that are not required/used during normal runtime, as well as "apt-mark auto" for those that aren't specifically-wanted, but are required by something else.
What has happened in my case, is that apt, dpkg, or both, have somehow ended up gnawing on the CM4 that I am using as my dev/programming workbench, rendering it inoperable and requiring reflashing.
This may be a scenario-specific thing, but what I would like to ask is, does such a toolchain or suite exist for taking Debian/RPi packages from the same source as Pi OS draws them, and install them on a volume/partition other than, and in full isolation from, the live filesystem, and to perform updates and maintenance on created images in the same manner as if apt would do on a live system?
Just to scratch the surface, I have been playing around with CM4s for quite a while now, I own three with differing specs (2G/32G, 1G/8G, 8G/8G), but now I have made a start of looking to create a custom, stripped-down, "deployment image" with a lower install and RAM footprint than Pi OS, with the consensus that the OS runs from a read-only root, and with updates done whilst the image is "offline", by ways of through another RPi device over USB (with the bootloader switch on), similar to how the Windows' DISM utility can service both online and offline images.
What I have attempted to do prior to making this post, is to use debootstrap, apt(-get) and dpkg on the destination volume (with apt -o Dir=${PWD}) to strip out the parts (including apt and dpkg themselves from the image) that are not required/used during normal runtime, as well as "apt-mark auto" for those that aren't specifically-wanted, but are required by something else.
What has happened in my case, is that apt, dpkg, or both, have somehow ended up gnawing on the CM4 that I am using as my dev/programming workbench, rendering it inoperable and requiring reflashing.
This may be a scenario-specific thing, but what I would like to ask is, does such a toolchain or suite exist for taking Debian/RPi packages from the same source as Pi OS draws them, and install them on a volume/partition other than, and in full isolation from, the live filesystem, and to perform updates and maintenance on created images in the same manner as if apt would do on a live system?
Statistics: Posted by jm6600 — Mon Sep 09, 2024 8:29 pm