I can confirm that on an up-to-date Saucy system, a brand new container
with the ubuntu template network doesn't work.
--
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/1204069
Title:
lxc
Please be so kind and merge 1.4.16-3 from Debian, which fixes this issue
(beside some small other once):
nagios-plugins (1.4.16-3) unstable; urgency=medium
* Fixed check_squid* command definitions
* Add double threshold to check_smtp (LP: #318703)
- 12_check_smtp_double_threshold.dpatch
This is fixed in version 1.5 of nagios-plugins
** Changed in: nagios-plugins
Importance: Unknown = Undecided
** Changed in: nagios-plugins
Status: Unknown = New
** Changed in: nagios-plugins
Remote watch: SourceForge.net Tracker #2555775 = None
** Changed in: nagios-plugins
I also don't feel that this is a high priority bug since, so far, we
do not recommend allowing unprivileged users to use containers.
Agreed. Especially because (currently) it's fairly easy to escape from
LXC when you have root access to the container.
I don't believe it would be a serious loss
** Changed in: nagios-plugins (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1244713
Title:
invalid syntax for check_ssh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
Wow, that was quick, good job guys =)
Thanks,
Tom
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1244713
Title:
invalid syntax for check_ssh plugin
To manage notifications
** Changed in: maas
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1234880
Title:
HP ilo4 consoles default to autodetect protocol, which doesn't
For those users, getting back to the old way would be a chmod away and I
asked Serge to make sure permissions would only be changed once and not
with every update, so it should be a one time thing.
As for security, while we don't currently say LXC is secure on Ubuntu,
we're not aware of any way
** Branch linked: lp:~andreserl/maas/fix_ipmi_lp1234880_1.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1234880
Title:
HP ilo4 consoles default to autodetect protocol, which
Quoting Ross Patterson (m...@rpatterson.net):
I can confirm that on an up-to-date Saucy system, a brand new container
with the ubuntu template network doesn't work.
Did you make sure that the brand new container was created with a
flushed cache? (Either rm -rf /var/cache/lxc/* or add '-- -F'
Hi Stéphane,
I can see at least three ways of escaping.
The first is using LXC through libvirt. I see that there's an Apparmor
profile for usr.bin.lxc-start, but AFAIK libvirt does not use lxc-start.
Also, libvirt does not load the lxc-containers profile (AFAIK).
This is proven by the fact that
*** This bug is a duplicate of bug 1241957 ***
https://bugs.launchpad.net/bugs/1241957
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1241957, so is being marked as such.
*** This bug is a duplicate of bug 1241957 ***
https://bugs.launchpad.net/bugs/1241957
Public bug reported:
I did do-dist-upgrade and this is what it showed me.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: squid3 3.3.8-1ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic
Right, libvirt-lxc isn't LXC (even though they sort of stole the name)
and is indeed completely unsafe...
As for the rest, I'm happy to report that you misread the apparmor profile and
that we thought of and blocked all of those from the beginning as is shown
below:
root@lxc-dev:/# echo abc
Good news.
However I must say that the documentation on LXC does not say that
libvirt is less secure than the official LXC:
https://help.ubuntu.com/13.10/serverguide/lxc.html#lxc-libvirt
So either libvirt should ship with an Apparmor profile for LXC, or a
warning should be added to the relevant
** Branch linked: lp:~hjd/ubuntu/trusty/multipath-tools/bug1231182
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1231182
Title:
kpartx-boot: Typo in package description:
Thanks for taking your time to report this issue and help making Ubuntu
better.
I have created a patch for this and submitted it for review.
** Changed in: multipath-tools (Ubuntu)
Status: New = In Progress
** Changed in: multipath-tools (Ubuntu)
Assignee: (unassigned) = Hans
This should be backported for 12.04, since most should be running LTS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1228649
Title:
noVNC doesn't work when offloaded to port 80 or
19 matches
Mail list logo
