** Changed in: dovecot (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1512131
Title:
Apparmor complains about multiple /run/dovecot file access
FTR, same behaviour with Serge's lxcfs "testing" branch with cgfs.
--
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/1514690
Title:
rebooting container with systemd >= 226 fails to create
That did not fix reboot yet. I filed bug 1514690 as it's a different
root cause apparenlty.
@Serge: there's nothing that should "stick around", it's a reboot after
all and everything including pid 1 gets restarted. It just seems that
the second boot can't create the init.scope cgroup as the "outsi
I'm setting this to high as this breaks autopkgtesting on armhf quite
badly.
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
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/15
Public bug reported:
Even after fixing bug 1497420 rebooting containers with systemd >= 226
(i. e. with supporting unified cgroups) does not work. Build a standard
xenial container (using the ubuntu template; e. g. "adt-build-lxc ubuntu
xenial"), start it:
sudo lxc-start -n adt-xenial -F
then
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1512185
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta-lts-vivid (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.n
Hi Joseph,
Happy to test upstream kernels, but this setup requires a 64-bit native
arm64/aarch64 kernel, which I can't see at the link provided - only
32-bit armhf kernels.
Currently we're running the kernel from the linux-generic-lts-wily
package:
Linux swirlix18 4.2.0-16-generic #19~14.04.1-Ub
[Expired for ceilometer (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ceilometer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceilometer in Ubuntu.
https://bug
[Expired for ceilometer (Ubuntu) because there has been no activity for
60 days.]
** Changed in: ceilometer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceilometer in Ubuntu.
https://bug
[Expired for bind9 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net
In case it wasn't clear, my patch is supposed to be for the
debian/ntpdate.if-up file. Also, I think the priority of this bug should
be higher, it was assigned 'low' when there was no clear problem caused
by the race. Systems booting with uncorrectable clock skew can be a
serious problem.
--
You
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1125726
Title:
boot-time race between /etc/network/if-up.d/ntpdate and
"/etc/init.d/ntp start"
To manage notificat
** Patch added: "Patch candidate for 15.10"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1514485/+attachment/4515824/+files/lp-1514485-wily-deb.diff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Tags added: regression-release wily
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1503418
Title:
[SRU] [REGRESSION] launching byobu from unity uses the terminal icon
rather than
** Changed in: cloud-init (Ubuntu Wily)
Assignee: (unassigned) => Ben Howard (utlemming)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1514485
Title:
[SRU] cloud-init shoul
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device naming ru
** Branch linked: lp:~hopem/neutron/kilo-lp1498370
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1498370
Title:
DHCP agent: interface unplug leads to exception
To manage notificat
Marking as "critical" owing to Azure instance death. Because Azure
instances consider ephemeral devices to be ephemeral per-boot, a stop,
resized, or fabric restarted instance may not come back if the instance
is presented with a new ephemeral device.
Linked branch has been tested.
** Changed in:
** Branch linked: lp:~hopem/neutron/kilo-lp1498370
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1498370
Title:
DHCP agent: interface unplug leads to exception
To manage notificat
** Changed in: lxc (Ubuntu Vivid)
Status: New => In Progress
--
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/1436723
Title:
Regression: Nested LXC is broken on Vivid
To manage no
** Changed in: lxc (Ubuntu Trusty)
Status: Incomplete => Fix Released
--
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/1386840
Title:
[SRU] failure to start a container
To manage
** Changed in: lxc (Ubuntu Precise)
Status: Confirmed => Invalid
--
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/1242074
Title:
lxc-ls shows wrong status
To manage notifications
** Changed in: lxc (Ubuntu Trusty)
Status: Triaged => Fix Released
--
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/1346815
Title:
lxc-clone causes duplicate MAC address and IP add
** Changed in: lxc (Ubuntu Trusty)
Status: Confirmed => Fix Released
--
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/1304936
Title:
lxc-clone doesn't replace the hostname in some
** Changed in: lxc (Ubuntu Trusty)
Status: Confirmed => Fix Released
--
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/1354375
Title:
lxc-snapshot destroys container
To manage noti
** Changed in: lxc (Ubuntu Precise)
Status: New => Won't Fix
--
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/1253669
Title:
unable to launch lxc application containers when droppi
** Changed in: lxc (Ubuntu Trusty)
Status: New => Fix Released
--
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/1304167
Title:
syntax error, trusty beta-2 cloud image
To manage no
** Changed in: lxc (Ubuntu Trusty)
Status: Triaged => Fix Released
--
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/1342960
Title:
comments in common.conf must be updated
To manag
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: (unassigned) => Ben Howard (utlemming)
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Wily)
Status: New => In Progress
** Changed in: cloud-init (Ubuntu Xenial)
Sta
** Changed in: lxc (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
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/1410876
Title:
Error executing lxc-clone: lxc_container: u
The verification of the Stable Release Update for juju-core has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for livecd-rootfs has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encou
This bug was fixed in the package juju-core - 1.24.7-0ubuntu1~15.04.1
---
juju-core (1.24.7-0ubuntu1~15.04.1) vivid; urgency=medium
* New upstream microrelease. (Lp: #1506652)
* Update dep8 tests from Xenial.
-- curtis.ho...@canonical.com (Curtis C. Hovey) Fri, 16 Oct 2015
17:5
This bug was fixed in the package livecd-rootfs - 2.349.1
---
livecd-rootfs (2.349.1) wily; urgency=medium
* cloud-images: revert to old device naming (LP: #1510345).
-- Ben Howard Thu, 29 Oct 2015 11:29:01 -0500
** Changed in: livecd-rootfs (Ubuntu Wily)
Status: Fix Com
The verification of the Stable Release Update for juju-core has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package juju-core - 1.25.0-0ubuntu1~15.10.1
---
juju-core (1.25.0-0ubuntu1~15.10.1) wily; urgency=medium
* No change backport to 15.10 (LP: #1510565).
-- Robie Basak Thu, 29 Oct 2015 11:25:46
+
** Changed in: juju-core (Ubuntu Wily)
Status:
Public bug reported:
We have released LXC 1.0.7 upstream:
https://linuxcontainers.org/lxc/news
This will be the eigth upstream bugfix release to hit trusty. The
upstream changes are detailed at the URL above.
The MRE was reviewed by Martin Pitt here:
https://lists.ubuntu.com/archives/technical-b
This bug was fixed in the package lxc - 1.0.7-0ubuntu0.10
---
lxc (1.0.7-0ubuntu0.10) trusty; urgency=medium
* Update the /proc/self/mountinfo no-symlink verification to accomodate
recursive mounts. (LP: #1509752)
-- Serge Hallyn Wed, 28 Oct 2015 12:21:38
-0500
** Changed
** Tags removed: verification-needed
** Tags added: verification-done
--
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/1509752
Title:
Bug in ensure_not_symlink() from 0003-CVE-2015-1335.p
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regr
Separated them based on upstream. Is that what you were looking for?
** Patch added: "python-novaclient_2.22.0-0ubuntu2.debdiff"
https://bugs.launchpad.net/cloud-archive/+bug/1499510/+attachment/4515779/+files/python-novaclient_2.22.0-0ubuntu2.debdiff
--
You received this bug notification
This bug was fixed in the package lxc - 1.1.5-0ubuntu1
---
lxc (1.1.5-0ubuntu1) xenial; urgency=medium
* New upstream bugfix release (1.1.5)
(LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619)
* Drop proxy detection from the autopkgtest exercise script.
-- Stéphane Grab
This bug was fixed in the package lxc - 1.1.5-0ubuntu1
---
lxc (1.1.5-0ubuntu1) xenial; urgency=medium
* New upstream bugfix release (1.1.5)
(LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619)
* Drop proxy detection from the autopkgtest exercise script.
-- Stéphane Grab
This bug was fixed in the package lxc - 1.1.5-0ubuntu1
---
lxc (1.1.5-0ubuntu1) xenial; urgency=medium
* New upstream bugfix release (1.1.5)
(LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619)
* Drop proxy detection from the autopkgtest exercise script.
-- Stéphane Grab
This bug was fixed in the package lxc - 1.1.5-0ubuntu1
---
lxc (1.1.5-0ubuntu1) xenial; urgency=medium
* New upstream bugfix release (1.1.5)
(LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619)
* Drop proxy detection from the autopkgtest exercise script.
-- Stéphane Grab
@serge
Sure, it's a patch to golang runtime. I'll put this on my todo list this
week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1501651
Title:
ARM chroot issues: fatal error: rt_
Sounds like we're agreed that this report concerns a serious bug with
security implications (insofar as any means of accidentally destroying
your environment is), but is not an exploitable vulnerability, does not
need a CVE assignment requested by the VMT and won't lead to any
official security adv
@arges,
did you want to push this patch into our package until it hits upstream?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1501651
Title:
ARM chroot issues: fatal error: rt_sigac
** Changed in: lxc (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
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/1261045
Title:
Security bugfix in lxc-sshd template: add ro to t
** Changed in: lxc (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
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/1322067
Title:
3.15.0-1.x breaks lxc-attach for unprivileged cont
** Changed in: bridge-utils (Ubuntu)
Assignee: Stéphane Graber (stgraber) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1313796
Title:
[No Network] ifupdo
Fixed through trusty-backports.
** Changed in: lxc (Ubuntu Trusty)
Status: Triaged => Fix Released
--
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/1347020
Title:
systemd does not
Public bug reported:
I was debugging something unrelated about automount which lead me to wanting to
know if had started:
$ service --status-all | grep autofs
[ - ] autofs
# ... other stuff snipped
But I then try,
$ sudo initctl status autofs
autofs start/running, process 1812
I looked at the
Indeed, I agree that there is no risk for a "malicious actor" to use this flow.
However there is a confirmed risk that an openstack admin can accidentally
delete backups which he should not delete (and it DID happen, sadly...), when
the admin is asked to launch scripts (ospurge) used to delete re
This worked for me in trusty with the proposed cloud-archive repository.
Before, when I restarted haproxy, I got an extra process:
root@juju-machine-2-lxc-0:~# service haproxy restart
* Restarting haproxy haproxy
...done.
root@juju-machine-2-lxc-0:~# ps fxaw|grep haproxy
32215 ?Ss
Public bug reported:
We have released LXC 1.1.5 upstream:
https://linuxcontainers.org/lxc/news
This will be the second and probably last upstream bugfix release to hit
vivid. The upstream changes are detailed at the URL above.
The MRE was reviewed by Martin Pitt here:
https://lists.ubuntu.com/ar
We'll be closing this one in favor of a new LXC 1.1.5 MRE.
** Changed in: lxc (Ubuntu Vivid)
Status: Fix Committed => Won't Fix
--
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/15033
Public bug reported:
We have released LXC 1.1.5 upstream:
https://linuxcontainers.org/lxc/news
This will be the second and probably last upstream bugfix release to hit
vivid. The upstream changes are detailed at the URL above.
The MRE was reviewed by Martin Pitt here:
https://lists.ubuntu.com/ar
This will be fixed with 1.0.8.
** Changed in: lxc (Ubuntu)
Status: Confirmed => In Progress
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bug
The other variable wasn't visible because you didn't export it.
** Changed in: lxc (Ubuntu)
Status: New => Invalid
--
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/1513698
Title:
While I agree there is a non-negligible risk presented by this behavior,
I don't see how a malicious actor could use this flaw to their
advantage. As such, it doesn't seem like something for which the
OpenStack Vulnerability Management Team would issue an official security
advisory.
--
You receiv
** Changed in: lxc (Ubuntu)
Importance: Undecided => Medium
--
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/1502604
Title:
autopkgtests fail in LXC testbed
To manage notifications ab
Any reason you're running those commands as the container PID1 instead
of starting the container and using lxc-attach to run the commands
inside it?
What you're doing right now is unsupported as neither chfn nor su are
init processes, so they will not know how to setup the container or
handled oth
Note that newer lxc-checkconfig knows to check for those modules in your
kernel config so it should report what you're missing.
--
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/1508577
Titl
Looks like you're running LXC on a system which doesn't have the needed
kernel options (in this case iptables modules).
This isn't a supported configuration. Closing this bug report.
** Changed in: lxc (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because y
*** This bug is a duplicate of bug 1240757 ***
https://bugs.launchpad.net/bugs/1240757
Quoting Kevin Dalley (1452...@bugs.launchpad.net):
> *** This bug is a duplicate of bug 1240757 ***
> https://bugs.launchpad.net/bugs/1240757
>
> I have now added
>
> listen-on-v6 { none; };
> re
** No longer affects: 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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
To manage notification
stgraber@dakara:~/data/code/lxc/lxd (stgraber/master)$ lxc-stop -n foo ;
lxc-destroy -n foo ; lxc-clone clean-machine foo
foo is not running
Container is not defined
Error: container clean-machine is not defined
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this
** Package changed: lxc (Ubuntu) => apparmor (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/1496877
Title:
apparmor profile fails to load in Ubuntu 15.04
To manage notificatio
** No longer affects: 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/1480411
Title:
rm -r * fails to delete directories when using overlayfs in a user-
namespace
To mana
Seems to work fine here:
root@ubuntu:~# timedatectl
Local time: Mon 2015-11-09 18:33:40 UTC
Universal time: Mon 2015-11-09 18:33:40 UTC
RTC time: n/a
Time zone: Etc/UTC (UTC, +)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
That's with a 15.10 contai
** No longer affects: 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/1439649
Title:
Pacemaker unable to communicate with corosync on restart under lxc
To manage notificati
So was this bug just about you reaching the quota and LXC failing then?
Just checking whether there's an actual bug we need to fix ASAP or if
it's just about better error handling.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because y
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
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/1471358
Title:
lxc-checkconfig shows Mainline PPA Wily-4.0.7 kernel m
*** This bug is a duplicate of bug 1182458 ***
https://bugs.launchpad.net/bugs/1182458
** This bug has been marked a duplicate of bug 1182458
ubuntu-cloud template: use simplestreams to add integrity verification
--
You received this bug notification because you are a member of Ubuntu
Ser
Closing this, we don't have any Ubuntu release with supported VZ anymore
(last was hardy).
** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.laun
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1339781
Title:
centos 7 needs setpcap capability
To manage notif
We're not going to fix this in LXC as the failure is obviously intended.
However with lxcfs we can now render /proc/swaps in a more consistent
way, including hiding swap for containers which shouldn't have any swap
access.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
--
You
root@blah-o24tmx0f:/# ls -ld /
drwxr-xr-x 1 root root 18 Nov 9 18:13 /
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
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
root@dakara:~# ps aux | grep lxc-dnsm
lxc-dns+1551 0.0 0.0 28204 1096 ?SOct31 0:18 dnsmasq -u
lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid
--listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253
--dhcp-no-override --ex
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
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/1267367
Title:
lxc-create shouldn't create container when template is
** Changed in: lxc (Ubuntu)
Status: Confirmed => Fix Released
--
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/1197303
Title:
lxc ubuntu-cloud template defaults to lucid when on >=
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1424143
Title:
lxc-net should attempt to use ip before ifconfig,
- What Ubuntu version are you using?
- What LXC version are you using?
- Is the container privileged or not?
- Where did you see this behavior (over ssh to the container, in a lxc-console
shell or in lxc-attach)?
That should help figure out what's going on a bit more.
** Changed in: lxc (Ubun
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Importance: Medium => Wishlist
--
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/1475751
Title:
ne
** Changed in: lxc (Ubuntu Wily)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu Xenial)
Status: Confirmed => Triaged
--
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/
Just re-read through this whole bug.
It looks like what broke your setup is actually a bugfix in LXC wrt
config inheritance.
Your config contains:
- lxc.mount.auto =
- lxc.mount.auto = cgroup:mixed
This instructs LXC (and that wasn't implemented right at first) to wipe all of
lxc.mount.auto,
Works fine here both privileged and unprivileged, so looks like we fix
this somehow in recent releases. I'll have this issue be closed with the
1.1.5 upload.
** Changed in: lxc (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
There was apparently a regression in Ubuntu 15.10 since I started
experiencing exactly the same problem with dovecot server failing to
start on system boot after upgrading my computer to release 15.10 (from
15.04):
$ sudo systemctl status dovecot.service
● dovecot.service - Dovecot IMAP/POP3 email
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1384783
Title:
Allow group-based entries in /etc/lxc/lxc-usernet
** No longer affects: 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/1402763
Title:
Multicast traffic not propating correctly over linux bridge
To manage notifications abo
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
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/1358306
Title:
lxc postinst incorrectly chooses network address to use
To
It absolutely does depend on it as the init script will fail to start if
it's not there.
Note that lxc-net can be turned off by the user and dnsmasq-base doesn't
install any daemon.
Marking this won't fix.
** Changed in: lxc (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this b
Unfortunately this isn't something that LXC itself can do, unless there
is some kind of .d mechanism where we can dump a bind config snippet
into.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.n
root@precise-gui:/# ls -lh /proc/sys/net/ipv4/ip_local_port_range
-rw-r--r-- 1 nobody nogroup 0 Nov 9 12:53
/proc/sys/net/ipv4/ip_local_port_range
root@precise-gui:/# uname -a
Linux precise-gui 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015
i686 i686 i386 GNU/Linux
So looks like
stgraber@dakara:~/data/code/lxc/lxc$ lxc-start-ephemeral -o blah -d | grep
"lxc-console" | awk '{print $NF}'
blah-psrfp_3s
Not the prettiest thing ever, but definitively doable with current
lxc-start-ephemeral.
I won't be spending more time on lxc-start-ephemeral though as we'll have the
new l
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
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/1181136
Title:
Empty log file when a container is started with the API
To
I guess I should look at backporting 1.0.8 back to precise which should
fix that.
--
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/1184936
Title:
lxc-clone freezes if copied container is
Hello Peter, or anyone else affected,
Accepted haproxy into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/1.5.14-1ubuntu0.15.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
1 - 100 of 163 matches
Mail list logo
