Comment 1 for bug 1608953

Thanks for the initial analysis! This is very helpful. I'm marking this as fixed in yakkety and add a xenial task.

I tried to reproduce this. I created a standard xenial and yakkety container:

  lxc launch images:ubuntu/xenial/amd64 x1
  lxc launch images:ubuntu/yakkety/amd64 y1

In both of them pid1's low fds look okay:

$ lxc exec x1 -- ls -l /proc/1/fd/{0,1,2}
lrwx------ 1 root root 64 Aug 18 05:10 /proc/1/fd/0 -> /dev/null
lrwx------ 1 root root 64 Aug 18 05:10 /proc/1/fd/1 -> /dev/null
lrwx------ 1 root root 64 Aug 18 05:10 /proc/1/fd/2 -> /dev/null

(same for y1)

PostgreSQL starts fine after installation:

$ lxc exec x1 -- apt install -y postgresql
$ lxc exec x1 -- pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
9.5 main 5432 online postgres /var/lib/postgresql/9.5/main /var/log/postgresql/postgresql-9.5-main.log

(again, same for y1)

The generator ran:

$ lxc exec x1 -- ls -lR /run/systemd/generator/postgresql.service.wants
/run/systemd/generator/postgresql.service.wants:
total 0
lrwxrwxrwx 1 root root 39 Aug 18 05:13 postgresql@9.5-main.service -> /lib/systemd/system/postgresql@.service

So I'm afraid I cannot reproduce this for testing the fix. This is a requirement for SRUs. Can you please describe how this can be reproduced?