I am running lxd on snap on debian stable with most of my container images being various variants of debian (stable, testing and sid) although I have one image of ubuntu:trusty.
I have been trying to get x2go working on some containers that I setup after I upgraded from lxd 2.xx to lxd 3.0. I have noticed some interesting behavior with differences between containers developed before the upgrade to lxd 3.0 and those developed after.
Containers developed before the upgrade to lxd 3.0 where a userID had been added AND x2go had been setup I am able to access the container remotely using x2go and am able to log into the user using # su userID and the prompt then reads $ userID. In the containers developed AFTER upgrading to lxd 3.0, on the other hand, not only am I not able to use x2go but when I log into the user using #su userID the prompt then reads $ (goofy system won’t let me create a blank space here!!!) (note that there is no userID). To make things even more interesting I had one container setup to use ubuntu trusty (I would like to test something where it was setup to run on ubuntu trusty and has never since been upgraded). This container was set up using lxd 2.xx without any added users. I started the container to check things and used useradd to add a userID. Then I stopped that container and copied it into a new version (using lxd 3.0) and started that. When I log into that container using # su userID - - - well the prompt is $ userID.
Somehow there is a difference between debian based containers and ubuntu based containers in lxd3.0.
How do I achieve this different ‘login’ prompt (if that is the issue) or what needs to be changed (or is this a bug)?