dracut needs to see crypto_LUKS devices in order to consider including systemd-cryptsetup in the initrd

Bug #2140415 reported by Dan Bungert
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin (Ubuntu)
Status tracked in Resolute
Resolute
New
Undecided
Unassigned
dracut (Ubuntu)
Status tracked in Resolute
Resolute
Invalid
Undecided
Unassigned
zfs-linux (Ubuntu)
Status tracked in Resolute
Resolute
Fix Released
Undecided
Unassigned

Bug Description

With debian/patches/ubuntu/4001-dracut-Open-and-mount-luks-keystore.patch applied, systemd-cryptsetup is a requirement.

Proceeding without goes poorly.

Revision history for this message
Dan Bungert (dbungert) wrote :
Revision history for this message
John Cabaj (john-cabaj) wrote :

2.4.0-1ubuntu2 -> 2.4.0-1ubuntu3 debdiff

Revision history for this message
John Cabaj (john-cabaj) wrote :

2.4.0-1ubuntu3 on its way to -proposed with proper dependencies added.

Revision history for this message
Dan Bungert (dbungert) wrote :

So declaring the dependency from zfs-dracut to systemd-cryptsetup seems like a good idea, but is insufficient. The decision to include systemd-cryptsetup in the initrd has regressed somehow between questing and now, any ideas?

Revision history for this message
Dan Bungert (dbungert) wrote :

Thanks John!

Changed in dracut (Ubuntu Resolute):
status: New → Fix Committed
Revision history for this message
Benjamin Drung (bdrung) wrote :

Looking at dracut itself: dracut-core suggests systemd-cryptsetup in questing (108-3ubuntu3) and that is the same for resolute (109-11ubuntu1). So it wasn't dracut that pulled in systemd-cryptsetup.

Revision history for this message
Dan Bungert (dbungert) wrote :
Revision history for this message
Dan Bungert (dbungert) wrote :
Revision history for this message
Benjamin Drung (bdrung) wrote :

In questing you can see crypt and systemd-cryptsetup. In resolute none of them. I suspect this check() code to be relevant:

```
    [[ $hostonly ]] || [[ $mount_needs ]] && {
        for fs in "${host_fs_types[@]}"; do
            [[ $fs == "crypto_LUKS" ]] && return 0
        done
        return 255
    }
```

The only relevant change between 108 and 109 is: https://github.com/dracut-ng/dracut-ng/pull/1673

Changed in zfs-linux (Ubuntu Resolute):
status: New → Fix Committed
Dan Bungert (dbungert)
Changed in dracut (Ubuntu Resolute):
status: Fix Committed → Invalid
Dan Bungert (dbungert)
summary: - zfs-dracut depends on systemd-cryptsetup
+ dracut needs to see crypto_LUKS devices in order to consider including
+ systemd-cryptsetup in the initrd
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package zfs-linux - 2.4.0-1ubuntu3

---------------
zfs-linux (2.4.0-1ubuntu3) resolute; urgency=medium

  * zfs-dracut depends on systemd-cryptsetup (LP: #2140415)
    - adding systemd-cryptsetup as zfs-dracut dependency

 -- John Cabaj <email address hidden> Wed, 04 Feb 2026 14:13:18 -0600

Changed in zfs-linux (Ubuntu Resolute):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.