It's possible to have 2 instances of the container managers running at the same time

Bug #1657490 reported by Christopher Townsend
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Released
Medium
Christopher Townsend
Trunk
Fix Released
Medium
Christopher Townsend
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

It's possible to have 2 instances of a container manager running at the same time. For example, launching a Libertine app in U8 will start libertine-lx{cd}-manager and then running libertine-container-manager operations in an ssh session will start another instance of libertine-lx{cd}-manager.

After some investigation, this is due to a systemd user dbus session now existing when in an ssh session, which is different than the Upstart session dbus used in the U8 session. So the service will start for each.

We need a way to figure out if U8 is running and use it's session dbus and if it's not running, don't use the libertine-lx{cd}-manager at all.

Related branches

Changed in libertine (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision 378, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.6+17.04.20170209-0ubuntu1

---------------
libertine (1.6+17.04.20170209-0ubuntu1) zesty; urgency=medium

  [ Larry Price ]
  * Get libertine-container-manager and libertine-launch working in a confined
    environment.
  * Create a special desktop file to satisfy the snappy store.
  * Update snap definition to include aliases, renamed commands, and internal
    desktop file.
  * Ensure absolute path lxd bind-mounts have a valid name by using the full
    path as a backup.
  * Refactor liblibertine as a client wrapper for libertined and bump version
    to 1.5.2.
  * Protect against containers that aren't started when running commands.
  * Migrate the list-apps subcommand to list application ids. (LP: #1657877)
  * Run the libertined integration test with its own dbus sesison to prevent
    collisions with running service.

  [ Chris Townsend ]
  * Discover if a session is running and if so, use it's dbus session to start
    the container manager. (LP: #1657490)
  * Replace all pylxd execute()'s with calls to 'lxc exec' as pylxd has
    performance issues in execute().
  * Add ability to freeze and unfreeze LXC/LXD containers. This is disabled by
    default for now. (LP: #1654355)
  * Add ability to enable and disable the freezing of LXC/LXD containers when
    not in use. (LP: #1654355)
  * Deprecate the lx[cd] managers and use libertined for managing the containers
    and move the actual starting and stopping of containers to the respective
    backends. (LP: #1660685)
  * Add a restart subcommand to libertine-container-manager. Also try to restart
    the container when adding/removing bind-mounts, if appropriate.
    (LP: #1654355)
  * Enable Xmir '-rootless' mode by default and remove using Matchbox for the
    window manager. (LP: #1662555)
  * Change when the libertine-xmir Upstart gets started to account for Unity 8
    now directly starting apps.
  * Bump release version to 1.6.

 -- Christopher Townsend <email address hidden> Thu, 09 Feb 2017 16:14:23 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.