cryptsetup-generator: do not bind to the decrypted device unit (#6538)

This breaks things when the decrypted device is not immediately
`SYSTEMD_READY=1` (e. g. when a multi-device btrfs system is placed on
multiple cryptsetup devices).

Fixes #6537.

diff --git a/src/cryptsetup/cryptsetup-generator.c b/src/cryptsetup/cryptsetup-generator.c
index cd07f2abd98eda6eaf9cfb9ad585789d3dfd83df..9ecb6e3566a25e895b5787e4ce90fb51250e1786 100644 (file)
--- a/src/cryptsetup/cryptsetup-generator.c
+++ b/src/cryptsetup/cryptsetup-generator.c
@@ -109,7 +109,6 @@ static int create_disk(
                        "SourcePath=/etc/crypttab\n"
                        "DefaultDependencies=no\n"
                        "Conflicts=umount.target\n"
-                       "BindsTo=dev-mapper-%i.device\n"
                        "IgnoreOnIsolate=true\n"
                        "After=cryptsetup-pre.target\n",
                        f);