hi Serge.
same problem here.
problem seems due to having a bridge already configured.
changed USE_LXC_BRIDGE to false in /etc/default/lxc solved it.
if it's not possible to handle an existing bridge during installation,
at least a more verbose error message would help.
--
You received this bu
** Changed in: lxc (Ubuntu)
Status: Invalid => Confirmed
--
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/939795
Title:
package lxc (not installed) failed to install/upgrade: subpr
more detailed information on how I installed lxc with a bridge already
configured:
# sudo aptitude install lxc
installation will abort (as in the first post)
edit /etc/default/lxc changing USE_LXC_BRIDGE from true to false.
# sudo aptitude remove lxc && sudo aptitude install lxc
that's it.
(
Public bug reported:
host: oneiric with server minimal install + lxc + bridge_utils (bridge manually
set up)
guest: oneiric
during creation:
I: Unpacking resolvconf...
W: Failure while installing base packages. This will be re-attempted up to
five times.
W: Failure while installing base packa
Public bug reported:
host: oneiric with server minimal install + lxc + bridge_utils (bridge manually
set up)
guest: oneiric
during creation:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "en_US:en",
LC_ALL = (unset),
Public bug reported:
host: oneiric with server minimal install + lxc + bridge_utils (bridge manually
set up)
guest: oneiric
every time the container is started /run/lock is missing.
I then create it manually, and next time is gone again.
** Affects: lxc (Ubuntu)
Importance: Undecided
Public bug reported:
host: oneiric with server minimal install + lxc + bridge_utils (bridge manually
set up)
guest: lucid
when shutting down the container (shutdown -h now from within or pkill
-INT lxc-start from the host) it does not stop completely
lxc-info show is still running
infact shut
commands:
sudo rm -fr /var/cache/lxc/oneiric
sudo lxc-create -t ubuntu -n test -f /etc/lxc/local.conf -- -r oneiric -a i386
errors during creation are shown only when container cache is
bootstrapped (but the problem is still there also when the cache is just
copied)
in the host:
cat /etc/networ
quick fix to lxc-ubuntu while waiting lxcguest to be fixed (just in
case...)
chroot $rootfs apt-get install --force-yes -y lxcguest
+ # fix for oneiric /var/lock
+ if [ $release = "oneiric" ]; then
+ sudo sed -i '/touch \/var\/run\/utmp/ i\
+mkdir -p \/run
I do agree. It's the same solution I adopted locally ;)
--
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/880020
Title:
oneiric container install problem: resolvconf
To manage notificatio
tested and now works as expected.
if a non-existing user is used, the creation is aborted (with a
message). if the user exists, or no user is declared, container is
created as usual.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc
tested and works as expected.
--
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/880020
Title:
oneiric container install problem: resolvconf
To manage notifications about this bug go to:
h
tested and now is ok.
--
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/880030
Title:
oneiric container problem: missing /run/lock
To manage notifications about this bug go to:
https://bu
any news on this?
--
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/820715
Title:
sudo poweroff -n within a container just hangs
To manage notifications about this bug go to:
https://bugs
why not in lxc-ubuntu template?
appending update repo to source-list, then updating (it's already doing
that anyway to install lxcguest) and upgrading openssh.
my 2c.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
http
enabling lucid-updates in a lucid container, updating and upgrading
throw errors with udev, dmsetup and plymouth:
Processing triggers for ureadahead ...
Setting up udev (151-12.3) ...
mknod: `/lib/udev/devices/ppp': Operation not permitted
dpkg: error processing udev (--configure):
subprocess ins
@serge: udev and coreutils are already installed in default lucid container.
if I add updates repo and just install openshh-server everything is
fine.
if I try to full-upgrade, or just try to install udev from lucid-
updates it throw
Setting up udev (151-12.3) ...
mknod: `/lib/udev/devices/ppp'
see:
http://www.emanuelis.eu/2010/09/15/mknod-lib-udev-devices-ppp-operation-
not-permitted-when-updating-ubuntu-10-04-on-virtual-lxc-machine/
--
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/bu
18 matches
Mail list logo
