Public bug reported:
The lxc-download template is missing the --keyserver option that is
mentioned in the usage description.
This makes it impossible to use the download template where HKP ports
are blocked by my firewall. By implementing this change, I was able to
use the template with a keyserv
There was an additional change on the same line (removing a letter, "patch"
-> "path" iirc). Did you include that change too?
Neil
On 18 Sep 2013 20:01, "Serge Hallyn" <1217...@bugs.launchpad.net> wrote:
> Thanks - the patch looks good. Unfortunately I dragged my feet too
> long, and we now no l
Here's my patch for raring.
I built the 64-bit debs and installed them in a chroot, everything looks fine.
I built the 32-bit debs in a 32-bit chroot and installed them, and they look
good too.
** Attachment added: "0016-fix-lxc-create-help-text"
https://bugs.launchpad.net/ubuntu/+source/lxc
Thanks Serge, that was exactly the help I was wanting.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1217730
Title:
lxc-create help text error
To manage notifications about this bug g
Public bug reported:
There is a typo in the output of
lxc-create --help
specifically the --lxcpath line has 2 issues:
1 It should start "-P, --lxcpath"
2 It says "patch" instead of "path"
$ lxc-create --help
usage: lxc-create -n NAME [-f CONFIG_FILE] [-t TEMPLATE] [FS_OPTIONS] --
The following command has done the trick:
sudo aptitude install lxc python3-lxc
I confirm that 0.9.0-0ubuntu3.4 has fixed the problem on raring.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Serve
neil@nbg-desktop:~$ apt-cache policy lxc
lxc:
Installed: 0.9.0-0ubuntu3.3
Candidate: 0.9.0-0ubuntu3.4
Version table:
0.9.0-0ubuntu3.4 0
500 http://gb.archive.ubuntu.com/ubuntu/ raring-proposed/universe amd64
Packages
*** 0.9.0-0ubuntu3.3 0
500 http://gb.archive.ubuntu.c
Is this going to be back-ported to raring?
If not, is there an alternative command I can use on the raring version
to do a similar thing to:
lxc-execute --name test /bin/bash
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubun
Sorry, I should have said: I confirm the fix works for me on saucy.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1188501
Title:
lxc-execute fails to start container without rootfs
To
Raised https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1188501
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/993706
Title:
Fix lxc-execute without rootfs failing apparmor transition
Public bug reported:
I get the following output when trying to start a container just running
bash as an app:
$ sudo lxc-execute --name test /bin/bash
lxc-execute: Permission denied - failed to change apparmor profile to
lxc-container-default
lxc-execute: invalid sequence number 1. expected 4
l
I guess given the release date that this fix is in Raring? Should I
raise a new bug since I'm getting a similar error in Raring?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/993706
Titl
Public bug reported:
bzr VCS handles hardlinked files, e.g. the checkout command has an
option to create hardlinks.
The warning message in pre-commit should no longer complain about
hardlinked files when using bzr as VCS.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: etckeeper 0.56ubuntu
** Patch added: "Suggested changes to pre-commit warning script"
https://bugs.launchpad.net/bugs/911155/+attachment/2655114/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/
I had this same problem. kvm-ok was reporting success, but the VM
creation was still failing. I had to power off the server after changing
the BIOS in order for the 'hvm' type to be valid.
--
libvirt.libvirtError: internal error no supported architecture for os type 'hvm'
https://bugs.launchpad.n
15 matches
Mail list logo
