FYI we're aware of an issue with bootstrapping Debian-based releases (trixie and bookworm) on recent versions of Bastille.
The source of this issue is found "upstream" of us, but we're looking into some workarounds.
Thank you to everyone that reported the issue and we appreciate your patience.
Which has me wondering whether I should even bother setting it up manually on this Bookworm debootstrap install I'm doing at the moment.
#Debian #debootstrap #Debian12 #DebianBookworm #systemd_boot
Nouvel article sur mon blog où je présente comment j'ai fait une installation personnalisée de Debian avec disque chiffré par LUKS v2, volumes Btrfs, systemd-boot et Secure Boot.
https://adorsaz.ch/articles/installation-personnalis%C3%A9e-de-debian.html
#debian #sbctl #secureboot #btrfs #debootstrap #luks
---
PS: Les réponses à ce message apparaîtront comme commentaire sous l'article.
Networking Tip: If your client says "No route to host" on some ports but not others, double-check your server's firewall configuration... for example, if you're trying to use UFW and something also installed firewalld behind your back, you're going to get very confusing symptoms that won't be fixed by asking UFW to flush your iptables and re-create them.
hmmm since I'll be using #debootstrap anyway, I might as well use systemd-boot instead of grub … 🤔
Hunting regressions as a Service: https://lists.debian.org/debian-release/2024/04/msg00498.html
Today's challenge: #debootstrap (and #DebianInstaller as a result) vs. #britney's force-hint feature.
I am looking at tools like #debootstrap and #mmdebstrap and cannot figure out how they know which core packages to include for a given distro/suite.
Is there a minimum list to build a VM/docker container somewhere?
Creating Sandboxes with systemd-nspawn and debootstrap
Exploring new #Linux features is exciting, but it can be risky! I sometimes break my system while testing packages. To avoid this, I recently tried #systemd-nspawn with #debootstrap - it's a lightweight #container that works well for isolated testing.
#Debian users, this guide shows you how to get systemd-#nspawn up and running, no fuss.
Installing the packages
First things first, we need to install two packages: systemd-container and debootstrap:
BastilleBSD 
KaiXin
scy
Cyril Brulebois
Adrien Dorsaz
Stephan Sokolow
moozer
Nayab Sayedsudo apt install systemd-container debootstrap
debootstrap lets you spin up a lightweight Debian right on your host, and systemd-container utilites such as systemd-nspawn and machinectl manage the OS in a lightweight container.
Create a Debian virtual machine
Let's generate a minimal Debian image called debian-testing with the following command:
sudo debootstrap --include=systemd,dbus stable /var/lib/machines/debian-testing
To verify successful installation, run machinectl list-images. Look for 'debian-testing' in the output.
Logging into virtual machine
Use the following command to start the debian-testing container.
sudo systemd-nspawn -D /var/lib/machines/debian-testing
Since you're now inside your virtual machine, let's set a password for the root user. This will come in handy when you want to manage the container using machinectl.
To swiftly terminate the container, press the Ctrl+] key combination three times in quick succession while inside the container.
Running a graphical application in vm
To run graphical apps like Chromium within the container, we need to set up display sharing. First, gracefully shut down the container. Then, use this command to establish the connection:
xhost local:; sudo systemd-nspawn -E DISPLAY="$DISPLAY" -D /var/lib/machines/debian-testing
Now that you're logged in, it's time to fire up Chromium! Just type the following commands to install and open it:
apt update
apt install chromium
chromium --no-sandbox
References
