Hi Igor,
I too am getting some errors like:
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing package libpam-systemd:amd64 (--configure):
subprocess installed post-installation script returned error exit status 100
But I do have TERM defined, so I'm not sure what is going on. Maybe it doesn't like my particular TERM setting (screen)? As far as not being able to find init scripts, that I would think is a packaging issue on the Ubuntu side maybe not defining the prereqs properly? <shrugs>
This does bring up another issue from my perspective. About daemon processes getting started within a bootstrap'ing.... hrmmm. Does anybody have thoughts on this?
Thanks!