Installing and running multiple instances of the same software

[Ralf Mardorf]

On Sun, 13 Mar 2016 16:15:28 +0300, Amer wrote:
>> On Mar 13, 2016, at 12:54 PM, Karl Auer <kauer at biplane.com.au> wrote:
>> If you start it as another user, won't you will be using a different
>> profile?

Correct, but some apps don't provide different profiles for a single
user.

>> To the OP: The discussion starts getting a bit esoteric here. I think
>> Ralf and I are agreed that you need some form of container to run
>> your two Vyatta's.

Correct.

>> kauer at kt:~$ less /usr/local/bin/chuser

It's a script I wrote myself, hence I posted it:

  On Sun, 13 Mar 2016 09:58:00 +0100, Ralf Mardorf wrote:
  >[rocketmouse at archlinux ~]$ grep -v "#" /usr/local/bin/chuser 
  >
  >
  >xhost +
  >gksudo -u chuser "$*"
  >xhost -
  >exit

It requires that you add a user named "chuser".

>> Thanks for the info on systemd-nspawn, that was new to me.

You are welcome! Once it was new to me too and somebody else gave me the
hint, perhaps Tom (subscribed to this list, but it was) on Debian users,
I don't remember exactly.

>> For this particular query though, do contained OSes get their own IP
>> addresses and so forth? How does sharing of network interfaces (and
>> devices more generally) work?

I don't know, but regarding /etc/resolv.conf for systemd-nspawn there
already is a difference if you launch it by

  systemd-nspawn -qD /mnt/moonstudio

or by

  systemd-nspawn -bqD /mnt/moonstudio

>> "Note that this is particularly dangerous if the container is
>> running a distribution with upstart, like Ubuntu, since programs
>> which talk to init, like shutdown, will talk over the abstract Unix
>> domain socket to the host's upstart, and shut down the host."

At least my Ubuntu 15.10 and my Arch Linux, both based on systemd,
shutdown the a container started by"systemd-nspawn -bqD /mnt/moonstudio"
and not the "host".

Regards,
Ralf