Permissions on the created lxc container somehow are reflecting the users /etc/password file:
ubuntu@dpb-local-landscape-client-0:~$ cat /etc/passwd |grep landscape landscape:x:104:109::/var/lib/landscape:/bin/false ubuntu@dpb-local-landscape-client-0:~$ ll /etc/landscape total 12 drwxr-xr-x 2 root root 4096 Oct 12 17:48 ./ drwxr-xr-x 86 root root 4096 Oct 12 17:47 ../ -rw------- 1 999 root 164 Oct 12 17:48 client.conf ubuntu@dpb-local-landscape-client-0:~$ logout Connection to 10.0.3.143 closed.
dpb@starbuck:dpb-local$ cat /etc/passwd |grep landscape landscape:x:999:999::/var/lib/landscape:/bin/false dpb@starbuck:dpb-local$
My hunch is where the tar happens from the mount of the downloaded image in lxc/templates/lxc-ubuntu-cloud
Permissions on the created lxc container somehow are reflecting the users /etc/password file:
ubuntu@ dpb-local- landscape- client- 0:~$ cat /etc/passwd |grep landscape x:104:109: :/var/lib/ landscape: /bin/false dpb-local- landscape- client- 0:~$ ll /etc/landscape dpb-local- landscape- client- 0:~$ logout
landscape:
ubuntu@
total 12
drwxr-xr-x 2 root root 4096 Oct 12 17:48 ./
drwxr-xr-x 86 root root 4096 Oct 12 17:47 ../
-rw------- 1 999 root 164 Oct 12 17:48 client.conf
ubuntu@
Connection to 10.0.3.143 closed.
dpb@starbuck: dpb-local$ cat /etc/passwd |grep landscape x:999:999: :/var/lib/ landscape: /bin/false dpb-local$
landscape:
dpb@starbuck:
My hunch is where the tar happens from the mount of the downloaded image in lxc/templates/ lxc-ubuntu- cloud