[Bug 1653973] Re: Creating an LXC type container fails

2017-01-12 Thread Christopher Townsend
** Changed in: libertine/trunk Status: Fix Committed => Fix Released ** Changed in: libertine/devel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-12 Thread Christopher Townsend
@ventrical, I assume your missing apps started with today's upgrade. Not sure how that would happen...could you open a new bug about your problem and in that bug include the libertine version you are using and also include the output of 'libertine-container-manager -i $container_id list-apps'

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-12 Thread ventrical
I had 6 existing containers on one install of zesty with .deb apps installed and the last update/upgrade wiped out all the apps in the containers and in xapps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-11 Thread Launchpad Bug Tracker
This bug was fixed in the package libertine - 1.5+17.04.20170105.1-0ubuntu1 --- libertine (1.5+17.04.20170105.1-0ubuntu1) zesty; urgency=medium [ Chris Townsend ] * Drop support for the Puritine click package as that is Vivid only and a Vivid Libertine branch exists for any

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-11 Thread Gerry Boland
Note sure where to put this: I installed silo 2341 as I was hitting this problem on my zesty machine, but now creating a container with container manager fails with: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user LxcContainer.py:254: ERROR:

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/libertine/libertine-ubuntu-zesty-2341 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653973 Title: Creating an LXC type container fails To manage notifications

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-05 Thread Christopher Townsend
** Changed in: libertine/trunk Status: Triaged => In Progress ** Changed in: libertine (Ubuntu) Status: Triaged => In Progress ** Changed in: libertine/trunk Assignee: (unassigned) => Christopher Townsend (townsend) ** Changed in: libertine (Ubuntu) Assignee:

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~townsend/libertine/release-1.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653973 Title: Creating an LXC type container fails To manage notifications about this bug go to:

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-04 Thread Libertine CI Bot
Fix committed into lp:libertine at revision None, scheduled for release in libertine, milestone Unknown ** Changed in: libertine Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1653973] Re: Creating an LXC type container fails

2017-01-04 Thread Launchpad Bug Tracker
** Branch linked: lp:~townsend/libertine/fix-create-lxc-log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653973 Title: Creating an LXC type container fails To manage notifications about this bug

[Bug 1653973] Re: Creating an LXC type container fails after setting up an LXD type container

2017-01-04 Thread Christopher Townsend
Ok, I have figured this out and this is a problem with the current upstream release (1.4.4) as well, so we'll need a hotfix for this. The problem is setting the lxc logging during the LibertineLXC init before the container creation is overriding LXC from looking for default.conf and thus, we have