[pkg-lxc-devel] problems with lxc on backports

[Evgeni Golov]

Hi Paul,

looping in pkg-lxc-devel at lists.alioth.d.o :)

On Wed, May 18, 2016 at 08:17:47PM +0200, Paul Gevers wrote:
> In order to create an Ubuntu xenial lxc, I upgraded lxc to the version
> in backports. I then successfully used a newly created Ubuntu container.
> However, then I wanted to use my already existing sid container again,
> but that failed to start properly (note the hassled text and the the
> tty1 & pts/0, I didn't note that until later):
> 
> paul at ruapehu ~ $ sudo lxc-start -d -n sid && sudo lxc-console -n sid
> 
> Connected to tty 1
> Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
> 
> 
> DDebieabni aGnN UG/NLUi/nLuixn usxt rsettrceht/cshi/ds isidd sid tty1
> 
>  sidpts/0
> 
> sid login:  login:
> Debian GNU/Linux stretch/sid sid pts/0
> 
> sid login: root
> 
> Login incorrect
> sid login: root
> 
> 
> After trying several time and with several of my other sid lxc (of which
> I am not sure of the password however), I (stupidly) decided to destroy
> the container and create a new one with the lxc-create from backports.
> Unfortunately that process doesn't tell me the new password (I assume
> now that it is root/root, but I started with my own system credentials).
> I couldn't log in to the new lxc as well.

No, root has no password anymore. If you want one: 
xc-attach -n foo -- passwd

> paul at ruapehu ~ $ LC_ALL=C.UTF-8 sudo lxc-create -n sid -t debian -- -r sid
> debootstrap is /usr/sbin/debootstrap
> Checking cache download in /var/cache/lxc/debian/rootfs-sid-amd64 ...
> Copying rootfs to /var/lib/lxc/sid/rootfs...insserv: warning: current
> start runlevel(s) (empty) of script `checkroot.sh' overrides LSB
> defaults (S).
> insserv: warning: current stop runlevel(s) (S) of script `checkroot.sh'
> overrides LSB defaults (empty).
> insserv: warning: current start runlevel(s) (empty) of script
> `checkroot.sh' overrides LSB defaults (S).
> update-rc.d: error: umountfs Default-Start contains no runlevels, aborting.
> insserv: warning: current start runlevel(s) (empty) of script
> `hwclock.sh' overrides LSB defaults (S).
> insserv: warning: current stop runlevel(s) (0 6 S) of script
> `hwclock.sh' overrides LSB defaults (0 6).
> update-rc.d: error: cannot find a LSB script for hwclockfirst.sh
> Creating SSH2 RSA key; this may take some time ...
> 2048 fa:44:b5:50:31:71:af:4a:da:c8:39:fa:47:61:5d:1e
> /etc/ssh/ssh_host_rsa_key.pub (RSA)
> Creating SSH2 DSA key; this may take some time ...
> 1024 30:57:ea:34:33:80:3b:3d:5e:30:ef:c9:22:8c:57:91
> /etc/ssh/ssh_host_dsa_key.pub (DSA)
> Creating SSH2 ECDSA key; this may take some time ...
> 256 63:55:38:5f:dc:ad:5c:41:55:ce:57:05:da:3a:6a:5c
> /etc/ssh/ssh_host_ecdsa_key.pub (ECDSA)
> Creating SSH2 ED25519 key; this may take some time ...
> 256 44:eb:95:58:ee:92:4a:a9:b8:be:54:23:52:af:5d:9b
> /etc/ssh/ssh_host_ed25519_key.pub (ED25519)
> Failed to read /proc/cmdline. Ignoring: No such file or directory
> invoke-rc.d: policy-rc.d denied execution of start.
> 
> Current default time zone: 'Europe/Amsterdam'
> Local time is now:      Tue May 17 21:11:40 CEST 2016.
> Universal Time is now:  Tue May 17 19:11:40 UTC 2016.
> 
> Generating locales (this might take a while)...
>   en_US.UTF-8... done
>   en_US.UTF-8... done
> Generation complete.
> paul at ruapehu ~ $ sudo lxc-start -d -n sid && sudo lxc-console -n sid
> 
> Connected to tty 1
> Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself
> 
> Debian GNU/Linux 8 sid tty1
> 
> sid login: paul
> Password:
> 
> Login incorrect
> sid login: paul
> Password:
> 
> Login incorrect
> sid login: root
> Password:
> 
> Login incorrect
> sid login: root
> Password:
> 
> Login incorrect
> 
> 
> Doing some web searching, it appears that I could get around the first
> bug by removing lib/systemd/system/container-getty at .service in the lxc,
> but that doesn't help (anymore) with the newly created lxc

"first bug"? the garbled screen one?

> Am I missing something? Is this a bug in the normal package as well?

The changelog/NEWS might add a blurb that there is no more default
password. But other than that I only see the initial bug with your old
container, but that's wiped now :( - can you provide input how it was
created? vanilla jessie lxc (1.0.x), lxc-create -t debian, upgrade to
lxc 2.0?