Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3848
** Bug watch added: github.com/canonical/cloud-init/issues #3848 https://github.com/canonical/cloud-init/issues/3848 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1917135 Title: System user cannot be created with a homedir Status in cloud-init: Expired Bug description: While it is not typical, system users can be created with a home directory by passing `-m/--create-home` flag to the command along with `-r/--system` flag. This cannot be done currently as `system: true` option will forcefully add the `-M` flag to the command. I think that there should be some way to do this other than manually calling `useradd`. I was expecting that if I put `homedir: /home/homeassistant` explicitly in the cloud-config, it will work, but it is not enough: ``` #cloud-config users: - default - name: homeassistant gecos: Home Assistant system: true lock_passwd: true homedir: /home/homeassistant ``` To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1917135/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp