The systemd-homed.service is a modern systemd daemon introduced to manage portable human user accounts. It allows for the creation of cryptographically secured home directories (e.g., using LUKS encryption) that are entirely self-contained, meaning a user’s data, configuration, and credentials can be migrated seamlessly between different Linux machines. While this is a fascinating feature for roaming desktop users or highly compartmentalized workstations, it is entirely unnecessary for standard Ubuntu Server deployments. For headless servers, web hosts, or containerized environments that rely on traditional /etc/passwd and LDAP/Active Directory for authentication, running a daemon designed for portable encrypted home directories wastes memory and adds an unnecessary attack surface to the OS.
This guide explains how to completely disable the systemd-homed service in Ubuntu Server, streamlining the user management stack and optimizing system resources.
Stop and Mask the systemd-homed Service
To guarantee that the server boots faster and ignores the portable home directory framework, we must disable the service and explicitly mask it to prevent systemd from invoking it during the boot sequence.
- Log into your Ubuntu Server via SSH using an account with
sudoprivileges. - First, check if the service is currently running or queued:
sudo systemctl status systemd-homed.service - Stop the service immediately (if it is active):
sudo systemctl stop systemd-homed.service - Next, disable the service to remove its symlinks from the systemd boot schedule:
sudo systemctl disable systemd-homed.service - For absolute certainty, explicitly mask the service. This symlinks the unit file to
/dev/null, creating a hard block against it starting under any circumstances:sudo systemctl mask systemd-homed.service
Verify the Service Lockdown
By masking systemd-homed.service, you guarantee that the Ubuntu OS will silently skip the initialization of the portable home directory management daemon, forcing the system to rely strictly on traditional POSIX account management.
To verify the lockdown is successful, attempt to start the service manually:
sudo systemctl start systemd-homed.serviceSystemd will return a fatal error stating that the unit is masked (e.g., Failed to start systemd-homed.service: Unit systemd-homed.service is masked). You have successfully neutralized the service, streamlining your server’s authentication pipeline.