Can't create vivid lxc on trusty

Bug #1445539 reported by Jason Hobbs
96
This bug affects 20 people
Affects Status Importance Assigned to Milestone
lxc (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

When I create a vivid lxc in trusty like this:

lxc-create -t ubuntu -n vivid-lxc -- -r vivid

I get this error at the end:

Hit http://archive.ubuntu.com vivid-updates/universe Translation-en │··························································································································
Reading package lists... Done │··························································································································
Reading package lists... Done │··························································································································
Building dependency tree... Done │··························································································································
Package lxcguest is not available, but is referred to by another package. │··························································································································
This may mean that the package is missing, has been obsoleted, or │··························································································································
is only available from another source │··························································································································
E: Package 'lxcguest' has no installation candidate │··························································································································

Tags: oil
Revision history for this message
Daniel Manrique (roadmr) wrote :

A partial workaround is to use the download template:

sudo lxc-create --name vivid -t download -- --dist ubuntu --release vivid --arch amd64

This yields a bootable container but it's still a bit weird: mine didn't get an IP address, one needs to lxc-attach to it and post-configure some items before it's usable via ssh as containers for other releases.

The ifup/ifdown scripts don't work because they're looking for files in /var/run which no longer exist; similarly, trying to dhclient eth0 fails with a problem setting up name resolution somewhere in /var/run: /etc/resolv.conf -> ../run/resolvconf/resolv.conf

So it's a bit flaky even with the download template.

Revision history for this message
Riccardo Padovani (rpadovani) wrote :

This happens also trying to create a wily lxc

Changed in lxc:
status: New → Confirmed
Revision history for this message
Riccardo Padovani (rpadovani) wrote :

So, it seems the default ubuntu template is broken.

A possible workaround is to download the template provided in the lxc's repo on GitHub[0] and replace to /usr/share/lxc/templates/lxc-ubuntu

Still, you have to configure network on your own

[0]: https://github.com/lxc/lxc/blob/master/templates/lxc-ubuntu.in

Revision history for this message
Riccardo Padovani (rpadovani) wrote :

Better, add the stable lxc ppa and it fixes the issue.

sudo apt-add-repository ppa:ubuntu-lxc/lxc-stable
sudo apt-get update
sudo apt-get dist-upgrade

Revision history for this message
Philipp Noack (philipp-noack-b) wrote :

I can confirm the comment of Riccardo, Trusty host and Wily template doesn't seem to work:

Package lxcguest is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'lxcguest' has no installation candidate

affects: lxc → lxc (Ubuntu)
Revision history for this message
Stéphane Graber (stgraber) wrote :

We're now relying on lxc-download which doesn't have such problems.
A backported version of lxc in trusty will work fine, though trusty is eol now.

Changed in lxc (Ubuntu):
status: Confirmed → Won't Fix
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.