what you describe is the first supported storage mechanism of homed
An individual LUKS2 encrypted loopback file for a user, stored in /home/*.home.
At login the file system contained in this files is mounted, after the LUKS2 encrypted volume has been attached. etc.
That is in my use case user janski and his home-directory works great:
systemd-homed: User record janski.identity is signed only by us, accepting.
systemd-homed: Added registered home for user janski.
The second storage mechanism is described as this
Similar, but the LUKS2 encrypted file system is located on regular block device, such as an USB storage stick. In this mode home directories and all data they include are nicely migratable between machines, simply by plugging the USB stick into different systems at different times.
And that is what I want to achieve with user archie. For that I generated the user on a different machine (pc-2) with the homectl options --image-path=PATH_TO_USB and --storage=LUKS and with some additional groups -G wheel,storage, etc.
User archie works perfect on pc-2 but when plugging the usb device into the other machine (pc-1)
I get the following homed error message
User record archie.identity is not signed at all, ignoring.
And when trying to activate user archie manually on pc-1 I get the following message
Operation on home archie failed: Failed to execute operation: Key has been revoked
That's where I'm right now and I wonder how to get user archie working on pc-1.