#debootstrap — Public Fediverse posts

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.

#FreeBSD #BastilleBSD #Debian #debootstrap

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.

#FreeBSD #BastilleBSD #Debian #debootstrap

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.

#FreeBSD #BastilleBSD #Debian #debootstrap

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.

#FreeBSD #BastilleBSD #Debian #debootstrap

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.

#FreeBSD #BastilleBSD #Debian #debootstrap

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

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

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

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

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

@richardh @LaurentChemla Not sure what you're talking about. If you're referring to #debootstrap's erroring out in the past few days because of a missing usrmerge/usr-is-merged package, see https://bugs.debian.org/1088212#46 — that's been fixed in unstable yesterday (1:52Z dinstall) and trixie a few hours later (7:52Z dinstall).

@richardh @LaurentChemla Not sure what you're talking about. If you're referring to #debootstrap's erroring out in the past few days because of a missing usrmerge/usr-is-merged package, see https://bugs.debian.org/1088212#46 — that's been fixed in unstable yesterday (1:52Z dinstall) and trixie a few hours later (7:52Z dinstall).

@richardh @LaurentChemla Not sure what you're talking about. If you're referring to #debootstrap's erroring out in the past few days because of a missing usrmerge/usr-is-merged package, see https://bugs.debian.org/1088212#46 — that's been fixed in unstable yesterday (1:52Z dinstall) and trixie a few hours later (7:52Z dinstall).

@richardh @LaurentChemla Not sure what you're talking about. If you're referring to #debootstrap's erroring out in the past few days because of a missing usrmerge/usr-is-merged package, see https://bugs.debian.org/1088212#46 — that's been fixed in unstable yesterday (1:52Z dinstall) and trixie a few hours later (7:52Z dinstall).

@richardh @LaurentChemla Not sure what you're talking about. If you're referring to #debootstrap's erroring out in the past few days because of a missing usrmerge/usr-is-merged package, see https://bugs.debian.org/1088212#46 — that's been fixed in unstable yesterday (1:52Z dinstall) and trixie a few hours later (7:52Z dinstall).

hmmm since I'll be using #debootstrap anyway, I might as well use systemd-boot instead of grub … 🤔

#Debian #systemd #grub

hmmm since I'll be using #debootstrap anyway, I might as well use systemd-boot instead of grub … 🤔

#Debian #systemd #grub

hmmm since I'll be using #debootstrap anyway, I might as well use systemd-boot instead of grub … 🤔

#Debian #systemd #grub

hmmm since I'll be using #debootstrap anyway, I might as well use systemd-boot instead of grub … 🤔

#Debian #systemd #grub

hmmm since I'll be using #debootstrap anyway, I might as well use systemd-boot instead of grub … 🤔

#Debian #systemd #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.

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.

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.

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.

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.

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:

sudo 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

• Tutorial: Systemd: The Adventure Continues - Lee Elston, The Linux Foundation: https://www.youtube.com/watch?v=-Tijw1SIXts. Slides: https://ossna2020.sched.com/event/c47t/tutorial-systemd-the-adventure-continues-lee-elston-the-linux-foundation
• https://wiki.debian.org/nspawn
• https://man7.org/linux/man-pages/man1/systemd-nspawn.1.html
• https://wiki.archlinux.org/title/Systemd-nspawn#Avoiding_xhost
• https://wiki.archlinux.org/title/systemd-nspawn
• https://man7.org/linux/man-pages/man1/machinectl.1.html

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:

sudo 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

• Tutorial: Systemd: The Adventure Continues - Lee Elston, The Linux Foundation: https://www.youtube.com/watch?v=-Tijw1SIXts. Slides: https://ossna2020.sched.com/event/c47t/tutorial-systemd-the-adventure-continues-lee-elston-the-linux-foundation
• https://wiki.debian.org/nspawn
• https://man7.org/linux/man-pages/man1/systemd-nspawn.1.html
• https://wiki.archlinux.org/title/Systemd-nspawn#Avoiding_xhost
• https://wiki.archlinux.org/title/systemd-nspawn
• https://man7.org/linux/man-pages/man1/machinectl.1.html

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:

sudo 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

• Tutorial: Systemd: The Adventure Continues - Lee Elston, The Linux Foundation: https://www.youtube.com/watch?v=-Tijw1SIXts. Slides: https://ossna2020.sched.com/event/c47t/tutorial-systemd-the-adventure-continues-lee-elston-the-linux-foundation
• https://wiki.debian.org/nspawn
• https://man7.org/linux/man-pages/man1/systemd-nspawn.1.html
• https://wiki.archlinux.org/title/Systemd-nspawn#Avoiding_xhost
• https://wiki.archlinux.org/title/systemd-nspawn
• https://man7.org/linux/man-pages/man1/machinectl.1.html

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:

sudo 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

• Tutorial: Systemd: The Adventure Continues - Lee Elston, The Linux Foundation: https://www.youtube.com/watch?v=-Tijw1SIXts. Slides: https://ossna2020.sched.com/event/c47t/tutorial-systemd-the-adventure-continues-lee-elston-the-linux-foundation
• https://wiki.debian.org/nspawn
• https://man7.org/linux/man-pages/man1/systemd-nspawn.1.html
• https://wiki.archlinux.org/title/Systemd-nspawn#Avoiding_xhost
• https://wiki.archlinux.org/title/systemd-nspawn
• https://man7.org/linux/man-pages/man1/machinectl.1.html

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:

sudo 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

• Tutorial: Systemd: The Adventure Continues - Lee Elston, The Linux Foundation: https://www.youtube.com/watch?v=-Tijw1SIXts. Slides: https://ossna2020.sched.com/event/c47t/tutorial-systemd-the-adventure-continues-lee-elston-the-linux-foundation
• https://wiki.debian.org/nspawn
• https://man7.org/linux/man-pages/man1/systemd-nspawn.1.html
• https://wiki.archlinux.org/title/Systemd-nspawn#Avoiding_xhost
• https://wiki.archlinux.org/title/systemd-nspawn
• https://man7.org/linux/man-pages/man1/machinectl.1.html

#Debian pre-seed late command tip… if you are using `apt-get install` commands to install packages into the new system in your `preseed/late_command` script:

use `in-target <COMMAND>` to run a command in the target, do NOT use `chroot /target <COMMAND>`.

Otherwise #debootstrap will complain about a bad file descriptor.

I think I've now got one of the #WICEN base computers installed from a USB stick almost fully automatically now.

Still some annoying prompts, but for the most part you can just hit ENTER to dismiss them.

#Debian pre-seed late command tip… if you are using `apt-get install` commands to install packages into the new system in your `preseed/late_command` script:

use `in-target <COMMAND>` to run a command in the target, do NOT use `chroot /target <COMMAND>`.

Otherwise #debootstrap will complain about a bad file descriptor.

I think I've now got one of the #WICEN base computers installed from a USB stick almost fully automatically now.

Still some annoying prompts, but for the most part you can just hit ENTER to dismiss them.

#Debian pre-seed late command tip… if you are using `apt-get install` commands to install packages into the new system in your `preseed/late_command` script:

use `in-target <COMMAND>` to run a command in the target, do NOT use `chroot /target <COMMAND>`.

Otherwise #debootstrap will complain about a bad file descriptor.

I think I've now got one of the #WICEN base computers installed from a USB stick almost fully automatically now.

Still some annoying prompts, but for the most part you can just hit ENTER to dismiss them.

#Debian pre-seed late command tip… if you are using `apt-get install` commands to install packages into the new system in your `preseed/late_command` script:

use `in-target <COMMAND>` to run a command in the target, do NOT use `chroot /target <COMMAND>`.

Otherwise #debootstrap will complain about a bad file descriptor.

I think I've now got one of the #WICEN base computers installed from a USB stick almost fully automatically now.

Still some annoying prompts, but for the most part you can just hit ENTER to dismiss them.

Hey #Debian / #Linux bubble.

I want to create an environment, where I can consume all applications I installed on my main system, and install (through means of apt) additional software - that is not started/supervised by systemd (as in LXC).

A #chroot / #debootstrap, without needing to use sudo to perform setting up the chroot.
I don't need the separation of containers (LXC, containersd), I just want to install some app so I can test something, which isn't installed on my base install.

@rml @hayley @ramin_hal9001 @awkravchuk @prahou
I'm also planning on using #debootstrap to host #veilid https://veilid.com . Whose current implementation is rust, tying in a little to our thread. I still haven't trapped the white smoke inside the boxen to do this though ;_;
Noted gopher://gopher.club gopher @kaixin (jiangjun right?) is assaying to install #OpenBSD

@kentpitman #poetry #climate this week https://climatejustice.social/@kentpitman/111148023329645586
https://www.nhplace.com/kent/PS/About-PS.html

@rml @hayley @ramin_hal9001 @awkravchuk @prahou
I'm also planning on using #debootstrap to host #veilid https://veilid.com . Whose current implementation is rust, tying in a little to our thread. I still haven't trapped the white smoke inside the boxen to do this though ;_;
Noted gopher://gopher.club gopher @kaixin (jiangjun right?) is assaying to install #OpenBSD

@kentpitman #poetry #climate this week https://climatejustice.social/@kentpitman/111148023329645586
https://www.nhplace.com/kent/PS/About-PS.html

@rml @hayley @ramin_hal9001 @awkravchuk @prahou
I'm also planning on using #debootstrap to host #veilid https://veilid.com . Whose current implementation is rust, tying in a little to our thread. I still haven't trapped the white smoke inside the boxen to do this though ;_;
Noted gopher://gopher.club gopher @kaixin (jiangjun right?) is assaying to install #OpenBSD

@kentpitman #poetry #climate this week https://climatejustice.social/@kentpitman/111148023329645586
https://www.nhplace.com/kent/PS/About-PS.html

@rml @hayley @ramin_hal9001 @awkravchuk @prahou
I'm also planning on using #debootstrap to host #veilid https://veilid.com . Whose current implementation is rust, tying in a little to our thread. I still haven't trapped the white smoke inside the boxen to do this though ;_;
Noted gopher://gopher.club gopher @kaixin (jiangjun right?) is assaying to install #OpenBSD

@kentpitman #poetry #climate this week https://climatejustice.social/@kentpitman/111148023329645586
https://www.nhplace.com/kent/PS/About-PS.html

@rml @hayley @ramin_hal9001 @awkravchuk @prahou
I'm also planning on using #debootstrap to host #veilid https://veilid.com . Whose current implementation is rust, tying in a little to our thread. I still haven't trapped the white smoke inside the boxen to do this though ;_;
Noted gopher://gopher.club gopher @kaixin (jiangjun right?) is assaying to install #OpenBSD

@kentpitman #poetry #climate this week https://climatejustice.social/@kentpitman/111148023329645586
https://www.nhplace.com/kent/PS/About-PS.html

Installing a somewhat custom #Debian system via #debootstrap from a Debian LiveCD, instead of using the installer. This feels very much like installing #Gentoo more than a decade ago.

#Linux

Installing a somewhat custom #Debian system via #debootstrap from a Debian LiveCD, instead of using the installer. This feels very much like installing #Gentoo more than a decade ago.

#Linux

Installing a somewhat custom #Debian system via #debootstrap from a Debian LiveCD, instead of using the installer. This feels very much like installing #Gentoo more than a decade ago.

#Linux

Installing a somewhat custom #Debian system via #debootstrap from a Debian LiveCD, instead of using the installer. This feels very much like installing #Gentoo more than a decade ago.

#Linux

Installing a somewhat custom #Debian system via #debootstrap from a Debian LiveCD, instead of using the installer. This feels very much like installing #Gentoo more than a decade ago.

#Linux

Okay, so I have a fairly special partitioning scheme, including /boot as LUKS1 and LVM with --raidintegrity.

Plan A: Install #Debian 12 via the netinst image. Doesn’t work because apparently the netinst kernel doesn’t support #dm_integrity.

Plan B: Install via a Debian LiveCD using Calamares. Doesn’t seem to work either, because Calamares apparently can’t handle my partitions and would love to create the partitioning itself, but lacks the options I require.

So … #debootstrap it is? 🤞😬

Okay, so I have a fairly special partitioning scheme, including /boot as LUKS1 and LVM with --raidintegrity.

Plan A: Install #Debian 12 via the netinst image. Doesn’t work because apparently the netinst kernel doesn’t support #dm_integrity.

Plan B: Install via a Debian LiveCD using Calamares. Doesn’t seem to work either, because Calamares apparently can’t handle my partitions and would love to create the partitioning itself, but lacks the options I require.

So … #debootstrap it is? 🤞😬

Okay, so I have a fairly special partitioning scheme, including /boot as LUKS1 and LVM with --raidintegrity.

Plan A: Install #Debian 12 via the netinst image. Doesn’t work because apparently the netinst kernel doesn’t support #dm_integrity.

Plan B: Install via a Debian LiveCD using Calamares. Doesn’t seem to work either, because Calamares apparently can’t handle my partitions and would love to create the partitioning itself, but lacks the options I require.

So … #debootstrap it is? 🤞😬

Okay, so I have a fairly special partitioning scheme, including /boot as LUKS1 and LVM with --raidintegrity.

Plan A: Install #Debian 12 via the netinst image. Doesn’t work because apparently the netinst kernel doesn’t support #dm_integrity.

Plan B: Install via a Debian LiveCD using Calamares. Doesn’t seem to work either, because Calamares apparently can’t handle my partitions and would love to create the partitioning itself, but lacks the options I require.

So … #debootstrap it is? 🤞😬

Okay, so I have a fairly special partitioning scheme, including /boot as LUKS1 and LVM with --raidintegrity.

Plan A: Install #Debian 12 via the netinst image. Doesn’t work because apparently the netinst kernel doesn’t support #dm_integrity.

Plan B: Install via a Debian LiveCD using Calamares. Doesn’t seem to work either, because Calamares apparently can’t handle my partitions and would love to create the partitioning itself, but lacks the options I require.

So … #debootstrap it is? 🤞😬