Where does this stand? A fully updated 12.04.1 system is still seeing lots of
interfaces;
2015 network-interface
4028 network-interface-security
and toggling an lxc container up and down four times seemed to result in
one extra network-interface and four extra network-interface-security's.
Thanks.
--
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/1065589
Title:
initctl list shows 11974 instances of network-interface-security
after two days of uptime
To manage
Public bug reported:
Some shops use x.509 certificates to restrict access to openssh.
(In fact, one shop I know of says that's how they kept a penetration tester
from getting too far.)
Upstream openssh refuses to support that feature because they feel it would
increase their attack surface (see
Public bug reported:
The local directories created by
sftp -r remotedir .
are unreadable by anybody, so when it tries to create anything in them, it
fails. Example:
$ sftp -r u...@host.com:foo foo
u...@host.com's password:
Connected to host.com.
Fetching /foo/ to foo
Retrieving /foo
Yeah, this fixes download, but there are worse problems with fedora
15:
--- lxc-fedora.orig 2012-08-27 14:08:55.870661264 -0700
+++ lxc-fedora 2012-08-27 14:09:01.93229 -0700
@@ -138,7 +138,12 @@
echo Failed to get a mirror
continue
fi
-
Public bug reported:
As discussed in the thread lxc template for RHEL?
http://sourceforge.net/mailarchive/message.php?msg_id=29730103
lxc-start-ephemeral only knows how to tweak the hostname for ubuntu and debian,
and needs to be taught about where rhel and centos put hostname, something like
For completeness, here's a cleaner copy of the patch, along with the
centos script I'm using, from that same thread.
I haven't actually deployed yet, but it passes my little unit test.
** Patch added: 0001-Add-Centos-support-to-lxc-create.patch
Public bug reported:
The ubuntu template has a handy --bindhome option, but that's not very useful
if you need to support
multiple guest OS's.
That option should be hoisted out of the template and into lxc-create itself.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
This seems wrong:
$ lxc-ls
demo_centos5 demo_centos6 demofedora16 demo_ubuntu_1004 demo_ubuntu_1204
demo_ubuntu_1204-temp-NjwI1BQ ubu12-bb-01-ubu12
ubu12-bb-01-ubu12 ubu12-bb-01-ubu12 ubu12-bb-01-ubu12 ubu12-bb-01-ubu12
ubu12-bb-01-ubu12 ubu12-bb-01-ubu12
This was on ubuntu 12.04 after doing apt-get dist-upgrade but before rebooting,
but I can still get it to happen after reboot, so it's still valid, I think.
I can reliably reproduce it by doing
sudo lxc-create -n demo_ubuntu_1204 -t ubuntu -- -r precise --bindhome $LOGNAME
lxc-start-ephemeral
I see a problem with just lxc-start, too, not lxc-start-ephemeral.
After doing
sudo lxc-start -n demo_ubuntu_1204
and then in another window
sudo lxc-console -n demo_centos6-temp-j4G0FcH
once I log in, the guest hangs, and lxc-ls shows
demo_ubuntu_1204 demo_ubuntu_1204-temp-JjkTzkK
Yeah, the hang only happens on users with nfs home directories.
I should file a separate bug for that.
Even on users with a local home directory, though, lxc-ls lists containers
multiple times
after starting and logging into a container. For instance,
$ lxc-ls
demo_ubuntu_1204
That's necessary, but not sufficient. There is still duplicate output even
with that change.
lxc-ls first lists all containers with ls -- /var/lib/lxc, and then,
inexplicably, also lists all active
containers with netstat. Why the duplication? Should it use sort -u?
--
You received this
Then perhaps the bug is in the manpage,
http://manpages.ubuntu.com/manpages/precise/en/man1/lxc-ls.1.html
which doesn't say anything about listing existing containers on one line, and
active containers on a second line.
--
You received this bug notification because you are a member of Ubuntu
I would be happy with (3), since the chasm between ubuntu and upstream
is so wide; I'd rather reduce the gap rather than widen it. Still want
a bug?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I find the old behavior confusing, and
http://www.greenhills.co.uk/2011/06/10/lxc.html seems to agree, it says
I’m going to skip lxc-ls because it’s needlessly confusing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Package changed: ubuntu = lxc (Ubuntu)
--
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/1051080
Title:
lxc-start-ephemeral hangs if bind mounting nfs homedir
To manage notifications
apport information
** Tags added: apport-collected precise
** Description changed:
On Ubuntu 12.04.1, ephemeral containers seem to conflict with NFS home
directories.
The user's home directory is on a remote NFS server.
The original container is created with
sudo lxc-create -t
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320836/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320837/+files/Lspci.txt
--
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/1051080
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320838/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320839/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320840/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320841/+files/UdevDb.txt
--
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/1051080
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1051080/+attachment/3320842/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
On an Ubuntu 12.04.1 system, each time you start and stop a container,
initctl status shows two more instances of network-interface and
network-interface-security running.
The numbers do not go down after the container shuts down.
Evidently there's an interface leak in
Running this script periodically seems to work around the problem. Only
lightly tested.
** Attachment added: gc.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396509/+files/gc.sh
--
You received this bug notification because you are a member of Ubuntu
Server
Oops, that only deleted one of the jobs. This draft deletes both.
** Attachment added: gc.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396518/+files/gc.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Once more with feeling.
** Attachment added: bug1065589-gc.sh
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1065589/+attachment/3396522/+files/bug1065589-gc.sh
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Alas, that archive doesn't show attachments. For the record, is there
a better archive somewhere?
--
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/1065589
Title:
initctl list shows
Public bug reported:
In ubuntu 12.04:
sudo lxc-create -t ubuntu -n foobar -- -r lucid
fails after a while. Workaround is sudo rm -rf /var/cache/lxc.
It'd be nice if it didn't go stale like that.
Log of the failure:
No config file specified, using the default config
debootstrap is
Public bug reported:
This is probably a dup of bug 1240757, created just so I could upload
the data requested in that bug report.
On a fresh, probably vanilla, ubuntu 14.04 server, I tried using ubuntu 14.04's
default lxc.
It created containers fine, but they failed to start, complaining
32 matches
Mail list logo
