homectl create user fails (Transport endpoint is not conected)

[Ginner]

I'm installing with the following relevant (imo) options:

LVM="true"
SYSTEMD_HOMED="true"
SYSTEMD_HOMED_STORAGE="luks"
BOOTLOADER="systemd"

Unfortunately it fails upon homectl create user with Operation on home <user> failed: Transport endpoint is not connected and homectl activate <user> with Operation on home <user> failed: No home for user <user> known and lastly cp -a /home/ginner.home/. /mnt/home/ginner.home fails with No such file or directory.

I think maybe you alludes to this in the code with:

    ### something missing, inside alis this not works, after install the user is in state infixated
    ### after install and reboot this commands work

I tried rebooting and running the commands manually, without luck.

Any help is very appreciated! Thank you for your excellent work on this 'script' :)

[picodotdev]

Relevant info to review alis commands with the provided configuration.

https://wiki.archlinux.org/title/Systemd-homed#LUKS_home_directory
https://gist.github.com/dbehnke/ad19ca8f1ccf80aebca5

[Ginner]

Good info. Now I'm in no way strong in this, but at what point in the code, is the IMAGE_PATH being mounted? Should it be included in the homectl create with the --image-path as briefly described in the first link?

Does it have to be initiated through luks cryptsetup? Maybe in if [ "$SYSTEMD_HOMED_STORAGE" == "luks" ]? Sorry, I'm just spitballing, I hope I'm not adding too much noise...

[picodotdev]

I think the problem is that systemd-homed for the luks storage expects the user home directory to be stored in "inside an encrypted LUKS volume inside a loopback file or any removable media".

For create the luks loopback file maybe the gist is usefull and maybe in --image-path/IMAGE_PATH must be specified that loopback file, but not sure also.

[Ginner]

Yeah, I think you're exactly right.

[picodotdev]

I think now should work as expected.

[Ginner]

Wow, You're fast :)
I've tested it, but after the password prompt following homectl create <USER> --enforce-password-policy=no --timezone=<TZ> --language=<LANG> --storage=luks --image-path=/mnt/home/<USER>.home --fs-type=ext4 - G wheel,storage,optical it fails with Operation on home <USER> failed: Transport endpoint is not conected.

It seems to me, that /mnt/home/<USER>.home is not mounted.

[picodotdev]

Another try to solve Transport endpoint is not conected. Some magic "sleep 5" inserted.

[Ginner]

Just tested it, same output.

I see the sleep 5 being run and it waits, however, I don't see a partition/image/filesystem for /home/<USER> being mounted anywhere in the code, is that right?

[picodotdev]

homectl create only creates user homed image not mounts it.

I will try again, I do my testing in VirtualBox. Are you trying in a virtual machine?

When fails, What is the output of this command for you? Is that service in good state?

systemctl status systemd-homed.service

[Ginner]

No, I'm testing on physical hardware.

Yeah, systemctl status systemd-homed.service returns 'Active (running)'.