I've just been able to reproduce this by following these steps:
```
$ lxc init ubuntu:x c1
$ lxc config set c1 raw.idmap "both 1000 1000"
$ lxc config device add c1 foo disk path=/home/ubuntu/foo
source=/home/daniel/jjl
$ lxc start c1
$ lxc exec c1 -- ls -lah /home/ubuntu
total 16K
drwxr-xr-x 4 root root 4.0K Feb 19 12:46 .
drwxr-xr-x 3 root root 4.0K Feb 19 12:46 ..
drwx------ 2 ubuntu ubuntu 4.0K Feb 19 12:46 .ssh
drwxr-xr-x 6 ubuntu ubuntu 4.0K Oct 23 2017 foo
```
Creation of the directory is performed by lxd before boot and therefore
before cloud-init runs. When cloud-init calls useradd, useradd sees
that the directory already exists and therefore doesn't do anything with
it (as it treats it as an existing home directory). This means that (a)
the user doesn't own the home directory (it is owned by root, the only
user in the container when the directory was created), and (b) the
contents of the skeleton directory don't get copied over to home
directory (because useradd, sensibly, doesn't want to overwrite any
existing files). As such, the workaround above is incomplete, because
the skeleton directory isn't copied over.
We've just spent some time discussing this at the sprint, and there
isn't a clear, quick solution; cloud-init doesn't know that this home
directory isn't _meant_ to already exist, and lxd doesn't know that it's
bind-mounting somewhere that's going to be a home directory once boot is
complete. We discussed that an alternate workaround would be to bind-
mount in to a non-home location and then re-bind (using cloud-config) in
a runcmd to the eventual destination. A more complete solution might
involve a lxd cloud-init data source, or lxd generating cloud-config to
perform the aforementioned new workaround transparently.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Low
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665943
Title:
Home directory has wrong ownership if created by lxd in arranging a
mount first
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1665943/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
