[Bug 1877382] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Can you show `snap changes`? ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877382 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1877382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
@Khaled yes, it is and we have it now. What's still needed is for the kernel to be signed so it can be used under secureboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876475] Re: lxc can't assign ipv4 address from lxc-container config file
Yes, different versions of different distros will have different behavior as to what they do with pre-existing network config. Point is, it's racy and unreliable, the only way to get guaranteed behavior is to make sure that nothing else attempts to manage the network when you've already pre-configured it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1876475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876475] Re: lxc can't assign ipv4 address from lxc-container config file
LXC always does the same thing, it preconfigures your network namespace. Now if the OS you're running in the container runs its own network configuration tool, that pre-made configuration will likely get reset or mangled. If you want to use those config keys, you need to make sure you're not running software in your container which will reset that pre-made configuration. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876475 Title: lxc can't assign ipv4 address from lxc-container config file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1876475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875182] Re: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
Is that within a privileged LXD container? If so, that's unfortunately a known snapd issue where the first snap you install in such a container will fail with that udev error, re-trying will succeed. ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875182 Title: package lxd 3.0.3-0ubuntu1~18.04.1 failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1875182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874878] Re: Did a "do-release-upgrade" from 18.04 to 20.04 and got an error message
Thanks for your analysis, I've re-targeted to snapd as that's not expected behavior from it. ** Package changed: lxd (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874878 Title: Did a "do-release-upgrade" from 18.04 to 20.04 and got an error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1874878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Ok, fixed the bug tasks and re-opened the bug as we still need this kernel to get signed. ** Changed in: linux-kvm (Ubuntu) Status: Fix Released => Triaged ** Changed in: cloud-images Assignee: Roufique Hossain (roufique) => (unassigned) ** Changed in: linux-kvm (Ubuntu) Assignee: Roufique Hossain (roufique) => (unassigned) ** Changed in: cloud-bl-tutorials Status: Confirmed => Invalid ** Changed in: cloud-bl-tutorials Status: Invalid => New ** Changed in: cloud-bl-tutorials Remote watch: Email to roufique@rtat # => None ** Project changed: cloud-bl-tutorials => linux (Ubuntu) ** No longer affects: linux (Ubuntu) ** Changed in: cloud-images Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hmm, actually, CONFIG_EFI_STUB is the one we were missing and I'm not seeing that in your VM either, which makes me wonder how it was booted in the first place :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-bl-tutorials/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Thanks Louis, so our testing may in fact have been accurate and things regressed afterwards :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-bl-tutorials/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Just tested it now, confirmed that this still boots fine and that this time the LXD agent successfully starts too. So this config seems suitable for us. That + enabling kernel signing will get us working images. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
** Description changed: The `disk-kvm.img` images which are to be preferred when run under - virtualization, completely fail to boot under UEFI. + virtualization, currently completely fail to boot under UEFI. - This is a critical issue as those are the images that LXD is now pulling - by default. + A workaround was put in place such that LXD instead will pull generic- + based images until this is resolved, this however does come with a much + longer boot time (as the kernel panics, reboots and then boots) and also + reduced functionality from cloud-init, so we'd still like this fixed in + the near future. + To get things behaving, it looks like we need the following config + options to be enable in linux-kvm: + + - CONFIG_EFI_STUB + - CONFIG_VSOCKETS + - CONFIG_VIRTIO_VSOCKETS + - CONFIG_VIRTIO_VSOCKETS_COMMON + + == Rationale == + We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. + + We also need the LXD agent to work, which requires functional virtio + vsock. + + == Test case == + - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz + - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img + - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 + - lxc launch bug1873809 v1 + - lxc console v1 + - + - + - lxc exec v1 bash + + To validate a new kernel, you'll need to manually repack the .img file + and install the new kernel in there. + + == Regression potential == + I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. + + Also, this will be introducing virtio vsock support which again, could + maybe confused some horribly broken systems? + + + In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. + + + -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 - Note that the non optimized images boot just fine (disk1.img). - - I've reproduced this issue with: - - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G - + - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img + - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE -
[Bug 1873809] Re: disk-kvm.img aren't UEFI bootable
Marking cloud-images side of this as Invalid since the images themselves are built correctly. Re-packing with an updated kernel boots just fine, so we only need to track this against linux-kvm. ** Changed in: cloud-images Status: New => Invalid ** Summary changed: - disk-kvm.img aren't UEFI bootable + Make linux-kvm bootable in LXD VMs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: disk-kvm.img aren't UEFI bootable
I've tested a kernel with CONFIG_EFI_STUB added (thanks cking!). This does boot with secureboot enabled, though the LXD agent fails to start due to lack of vsock. So in addition to CONFIG_EFI_STUB, it looks like we also need: - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON Which should give us the bits needed for virtio vsock. The rest all looked good, so we should be fine with those tweaks and the kernel getting signed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: Make linux-kvm bootable in LXD VMs To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873809] Re: disk-kvm.img aren't UEFI bootable
Ok, so the fact that we thought this worked is clearly the result from bad testing on our part, probably because of our simplestreams parsing code we fixed yesterday... We obviously still need to move LXD onto this images as booting the non- kvm images takes twice as long as it should (due to them panic + reboot every time) AND also breaks cloud-init, at least in the way we'd like to use it. Now realistically this can't be fixed in time for 20.04, so what we've done is submitted a change to simplestreams to force all LXD users onto the non-kvm image: https://code.launchpad.net/~stgraber/simplestreams/+git/simplestreams/+merge/382597 We'll also tell all users of `ubuntu:` and `ubuntu-daily:` that they need to do: - lxc config device add NAME config disk source=cloud-init:config Which passes a stable config drive to cloud-init, avoiding the cloud- init issue they'd be getting out of the box. Moving forward, we'd like the -kvm kernel to be both EFI enabled AND signed. This will then allow those images to work properly inside LXD, at which point we can undo the simplestreams change and have those images used once again by our users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: disk-kvm.img aren't UEFI bootable To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873362] Re: [FFe] remove ubuntu-support-status as its a confusing mess
** Summary changed: - remove ubuntu-support-status as its a confusing mess + [FFe] remove ubuntu-support-status as its a confusing mess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873362 Title: [FFe] remove ubuntu-support-status as its a confusing mess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1873362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873362] Re: remove ubuntu-support-status as its a confusing mess
Sounds fine, will this be covered in the release notes with a pointer to whatever replaces it? I've seen many users use/rely on this tool, so silently dropping it will be confusing and should be covered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873362 Title: remove ubuntu-support-status as its a confusing mess To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1873362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872098] Re: Installing nftables empties the current ruleset
That behavior was last confirmed on Ubuntu 18.04 with nftables 0.8.2-1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872098 Title: Installing nftables empties the current ruleset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1872098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872098] [NEW] Installing nftables empties the current ruleset
Public bug reported: The LXD snap has its own logic to directly add rules to nftables and so doesn't need "nftables" installed on the system. The problem is that if one is to install the package, the entire ruleset gets flushed at that point in time, breaking all LXD instances until LXD is reloaded and it re-adds itself to the ruleset. I can't think of a good reason why the ruleset would be flushed upon installation and nftables in general ought to be careful about pre- existing rules as there are many tools handling their own set of rules. ** Affects: nftables (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872098 Title: Installing nftables empties the current ruleset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1872098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container
https://github.com/lxc/lxd/pull/7167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871487 Title: anon_inode:[eventfd] leaked on vgs invocation inside lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container
The main leak was in dqlite and has now been included in master, the next rebuild of the snap (likely later today) will include it. ** Changed in: lxd (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871487 Title: anon_inode:[eventfd] leaked on vgs invocation inside lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container
https://github.com/canonical/raft/pull/123 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871487 Title: anon_inode:[eventfd] leaked on vgs invocation inside lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Ok, can you post the output of "ls -lh /proc/PID/fd/" where PID is the PID of the "lxd --logfile ..." process and the PID of the "daemon.start" script (lxd's parent process)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871487 Title: anon_inode:[eventfd] leaked on vgs invocation inside lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Can you show `lxc info` please as well as `ls -lh /proc/self/fd` inside that "reproducer" container? I just tested it here and I'm seeing: ``` root@bionic:~# ls -l /proc/self/fd total 0 lrwx-- 1 root root 64 Apr 9 20:57 0 -> /dev/pts/1 lrwx-- 1 root root 64 Apr 9 20:57 1 -> /dev/pts/1 lrwx-- 1 root root 64 Apr 9 20:57 2 -> /dev/pts/1 lr-x-- 1 root root 64 Apr 9 20:57 3 -> /proc/7458/fd ``` Which is the normal set of fds and so wouldn't trigger the LVM warning. ** Changed in: lvm2 (Ubuntu) Status: New => Invalid ** Changed in: lxd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871487 Title: anon_inode:[eventfd] leaked on vgs invocation inside lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871652] Re: Daemon snaps not properly stopped in some cases
Reproducer on arm64 at least: ``` root@c2400:~# lxc launch images:ubuntu/bionic test-snapd --vm -c security.secureboot=false -c limits.memory=16GB -c limits.cpu=5-12 Creating test-snapd Starting test-snapd root@c2400:~# lxc exec test-snapd bash root@test-snapd:~# sed "s/ports.ubuntu/us.ports.ubuntu/g" -i /etc/apt/sources.list root@test-snapd:~# apt update Get:1 http://us.ports.ubuntu.com/ubuntu-ports bionic InRelease [242 kB] Get:2 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB] Get:3 http://us.ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB] Get:4 http://us.ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages [975 kB] Get:5 http://us.ports.ubuntu.com/ubuntu-ports bionic/main Translation-en [516 kB] Get:6 http://us.ports.ubuntu.com/ubuntu-ports bionic/restricted arm64 Packages [664 B] Get:7 http://us.ports.ubuntu.com/ubuntu-ports bionic/restricted Translation-en [3584 B] Get:8 http://us.ports.ubuntu.com/ubuntu-ports bionic/universe arm64 Packages [8316 kB] Get:9 http://us.ports.ubuntu.com/ubuntu-ports bionic/universe Translation-en [4941 kB] Get:10 http://us.ports.ubuntu.com/ubuntu-ports bionic/multiverse arm64 Packages [126 kB] Get:11 http://us.ports.ubuntu.com/ubuntu-ports bionic/multiverse Translation-en [108 kB] Get:12 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages [650 kB] Get:13 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main Translation-en [314 kB] Get:14 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/restricted arm64 Packages [1064 B] Get:15 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/restricted Translation-en [10.9 kB] Get:16 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 Packages [949 kB] Get:17 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/universe Translation-en [330 kB] Get:18 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse arm64 Packages [3304 B] Get:19 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/multiverse Translation-en [4728 B] Get:20 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 Packages [444 kB] Get:21 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/main Translation-en [220 kB] Get:22 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/restricted arm64 Packages [668 B] Get:23 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/restricted Translation-en [8804 B] Get:24 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 Packages [583 kB] Get:25 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/universe Translation-en [218 kB] Get:26 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/multiverse arm64 Packages [1848 B] Get:27 http://us.ports.ubuntu.com/ubuntu-ports bionic-security/multiverse Translation-en [2764 B] Fetched 19.1 MB in 7s (2803 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 4 packages can be upgraded. Run 'apt list --upgradable' to see them. root@test-snapd:~# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-4.15.0-96 linux-headers-4.15.0-96-generic linux-image-4.15.0-96-generic linux-modules-4.15.0-96-generic The following packages will be upgraded: linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual 4 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 32.2 MB of archives. After this operation, 161 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-headers-4.15.0-96 all 4.15.0-96.97 [11.0 MB] Get:2 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-headers-4.15.0-96-generic arm64 4.15.0-96.97 [767 kB] Get:3 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-modules-4.15.0-96-generic arm64 4.15.0-96.97 [12.1 MB] Get:4 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-image-4.15.0-96-generic arm64 4.15.0-96.97 [8358 kB] Get:5 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-virtual arm64 4.15.0.96.87 [1860 B] Get:6 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-image-virtual arm64 4.15.0.96.87 [2448 B] Get:7 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-headers-virtual arm64 4.15.0.96.87 [1844 B] Get:8 http://us.ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 linux-headers-generic arm64 4.15.0.96.87 [2432 B]
[Bug 1871652] [NEW] Daemon snaps not properly stopped in some cases
Public bug reported: This bug leads to data loss and corrupted filesystems! Over the past few months/years, we've had occasional reports that users see their systems stuck on a 10min "stopping LXD snap" type message from systemd. We always thought it was our fault so added a lot of fallback logic and logging to our shutdown path to figure out what's going on. However in those cases, no sign of the shutdown logic was really reported, making it very odd. Because that usually happens when no more shells or SSH connections are running, figuring out what was going on took a LONG time. As mentioned in https://github.com/lxc/lxd-pkg-snap/issues/39, I've finally succeeded yesterday, having a system where this is reproducible AND where I can keep a shell. The process list looked like: ``` root 1 0.1 0.0 161464 8680 ?Ss 17:30 0:18 /sbin/init root 262 0.0 0.0 26296 8384 ?Shttps://bugs.launchpad.net/bugs/1871652 Title: Daemon snaps not properly stopped in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1871652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871652] Re: Daemon snaps not properly stopped in some cases
``` root@buildd08:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic root@buildd08:~# dpkg -l | grep snapd ii snapd 2.42.1+18.04 arm64Daemon and tooling that enable snap packages root@buildd08:~# snap list Name VersionRevTracking Publisher Notes core 16-2.44.1 8937 latest/stable canonical✓ core lxd 4.0.0 14364 latest/candidate canonical✓ - root@buildd08:~# snap version snap2.44.1 snapd 2.44.1 series 16 ubuntu 18.04 kernel 5.3.0-46-generic root@buildd08:~# ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871652 Title: Daemon snaps not properly stopped in some cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1871652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857046] Re: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3
Considering fixed as we now have 4.0.1 in the archive, if this still happens, let us know. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857046 Title: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870539] Re: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2
This has already been fixed in 4.0.1-0ubuntu1 ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870539 Title: package liblxc-common 3.0.4-0ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/ja/man1/lxc-user-nic.1.gz', que também está no pacote lxc-utils 3.0.4-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1870539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
https://github.com/gTile/gTile/issues/124 ** Bug watch added: github.com/gTile/gTile/issues #124 https://github.com/gTile/gTile/issues/124 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870354] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed()
Tracked it down to gTile being the issue actually, disabling that one with the rest of them on seems to fix it. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870354 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_text_align() from _st_set_text_from_style() from st_label_style_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869330] Re: Hangs after eoan -> focal release upgrade on shutdown
Wrong package as that's against the LXD snap and not any archive package. The issue sounds like: https://github.com/lxc/lxd-pkg-snap/issues/39 If you have any idea on how to reliably reproduce the issue, please comment in the Github issue as it's something we'd really like to get rid of... ** Bug watch added: github.com/lxc/lxd-pkg-snap/issues #39 https://github.com/lxc/lxd-pkg-snap/issues/39 ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869330 Title: Hangs after eoan -> focal release upgrade on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860813] Re: LXC container reports spike in swap occasionally
Hello Kellen, or anyone else affected, Accepted lxcfs into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxcfs/3.0.4-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: lxcfs (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: lxcfs (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860813 Title: LXC container reports spike in swap occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1860813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860813] Please test proposed package
Hello Kellen, or anyone else affected, Accepted lxcfs into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxcfs/3.0.3-0ubuntu1~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860813 Title: LXC container reports spike in swap occasionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1860813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869661] Re: lxc 3.23 (?) breaks nested lxd with snaps
This is now fixed in all channels and our own validation now checks for this too. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869661 Title: lxc 3.23 (?) breaks nested lxd with snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867535] Re: [FFe] LXC 4.0.0 LTS
The release announcement finally got pushed out here: https://discuss.linuxcontainers.org/t/lxc-4-0-lts-has-been-released/7182 The main new features are: - cgroups: Full cgroup2 support - cgroups: Freezer support in CGroup2 - cgroups: eBPF device controller support in CGroup2 - config: Add lxc.autodev.tmpfs.size configuration key - config: Add lxc.selinux.context.keyring key - config: Add lxc.keyring.session - file utils: Add fopen_cached() and fdopen_cached - api: Add new init_pidfd() member - memory utils: Add new cleanup api - lxc-usernsexec: Make it easy to map own uid - seccomp: Add s390 support - syscalls: Improve manual syscall implementations - network: Improved network device creation and removal - network: Allow moving wireless devices Only one symbol was added compared to 3.2.1: - init_pidfd (to retrieve the pidfd of the init process) And a total of 5 since 3.0.0: - mount (to inject mounts into a running container) - umount (to remove mounts from a running container) - seccomp_notify_fd (to support syscall interception) - init_pidfd (to retrieve the pidfd of the init process) - lxc_has_api_extension (to check whether particular feature/options are present) No rebuilds are needed and all reverse dependencies of liblxc are know to work properly. LXC upstream has auto-generated PPAs that are used on all of our CI systems (running 18.04) so we have been testing those upgrades continuously and don't expect any issue. No configuration keys were removed in this release (unlike 3.0) and so no config updates are required for our users. Existing 3.0 users can upgrade to 4.0, running containers will keep working and the default configurations used by 4.0 are even backward compatible to 3.0, so a downgrade is even an option if needed. As mentioned above, the main benefit of getting 4.0 in Ubuntu is to get the 5 years of upstream security updates. Even though LXC is in universe, it's still quite widely used and actively maintained in Ubuntu by us. It's also worth noting that we've had all LXD users running the LXD snap run LXC 4.0 for the past week with only one regression found in the attach logic. This has since been fixed and will be cherry-picked in the package that's to be uploaded to Ubuntu. We realize we're getting late in the cycle, ideally we'd like this uploaded as soon as possible so it can get built, go through autopkgtest and land in the archive as soon as the freeze lifts (if it's covered by the freeze at all, not sure). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867535 Title: [FFe] LXC 4.0.0 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1867535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869661] Re: lxc 3.23 (?) breaks nested lxd with snaps
Hmm, I thought we pushed all the nesting fixes to stable on Friday. Our own nesting tests are all clean but it's possible we're not hitting this particular exec case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869661 Title: lxc 3.23 (?) breaks nested lxd with snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659590] Re: containers won't start after lxc and apparmor upgrades in trusty
** Changed in: lxc (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659590 Title: containers won't start after lxc and apparmor upgrades in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240757] Re: Bridge not created if bind9 is on
** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240757 Title: Bridge not created if bind9 is on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1240757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1389954] Re: Make .lxc domain name resolution easier to discover and enable
** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389954 Title: Make .lxc domain name resolution easier to discover and enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569679] Re: lxc failed to do lxc-checkpoint again
** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569679 Title: lxc failed to do lxc-checkpoint again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1569679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575757] Re: Can't install kernel-nfs-server inside lxc container
There's nothing particularly safe for us to do here out of the box. Using an alternative profile or appending to the profile (in LXD's case) is your best bet. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575757 Title: Can't install kernel-nfs-server inside lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1575757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659590] Re: containers won't start after lxc and apparmor upgrades in trusty
anyone still affected by this? ** Changed in: lxc (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659590 Title: containers won't start after lxc and apparmor upgrades in trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760848] Re: lxc-create can't create bionic container on xenial
We're now using distrobuilder to build pre-made images avoiding the mess that was those scripts. ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760848 Title: lxc-create can't create bionic container on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861880] Re: lxc-attach command does not return error exit code if the command is failed
** Changed in: lxc (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861880 Title: lxc-attach command does not return error exit code if the command is failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1861880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858799] Re: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
** Changed in: lxc (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858799 Title: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1858799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866124] Re: ps -eo lxc no longer shows a task's lxc container
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866124 Title: ps -eo lxc no longer shows a task's lxc container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1866124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787436] Re: lxc 3.0.1-0ubuntu2 ADT test failure with linux 4.18.0-5.6
Based on autopkgtest history, this must have gotten fixed somehow. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787436 Title: lxc 3.0.1-0ubuntu2 ADT test failure with linux 4.18.0-5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1787436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776381] Re: lxc-test-api-reboot will hang with autopkgtest
It's not currently failing based on recent logs anyway. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776381 Title: lxc-test-api-reboot will hang with autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828255] Re: It's too easy to accidentally delete a container rather than a snapshot
There is configurable prompting for those that want it. We also refuse to delete running containers. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828255 Title: It's too easy to accidentally delete a container rather than a snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1828255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794523] Re: lxc-net.service is not properly ordered with network-online.target
Hmm, no, that would be wrong. Wants=/Requires= would cause lxc-net to not start if network- online.target is missing or if it fails. We only want to start after it if it does exist, which is what After does. ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794523 Title: lxc-net.service is not properly ordered with network-online.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840639] Re: Version 3.0.3 breaks lxc-usernsexec
What are your subuid/subgid allocations like? ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840639 Title: Version 3.0.3 breaks lxc-usernsexec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1840639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857046] Re: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3
@brauner any idea what that's about? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857046 Title: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837537] Re: FTBFS since lxc has different version numbers in Debian and Ubuntu
So I think I'll be doing the epoch bump with 4.0 which should help somewhat. There will still be the issue of not having the binary packages themselves lined up (different names) but that should be a step forward. ** Changed in: lxc (Ubuntu) Status: New => In Progress ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837537 Title: FTBFS since lxc has different version numbers in Debian and Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lxc/+bug/1837537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843383] Re: lxc, please bump epoch to 1
*** This bug is a duplicate of bug 1837537 *** https://bugs.launchpad.net/bugs/1837537 ** This bug has been marked a duplicate of bug 1837537 FTBFS since lxc has different version numbers in Debian and Ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843383 Title: lxc, please bump epoch to 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1843383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508744] Re: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508744 Title: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700500] Re: lxc-net incompatible with systemd-resolved
** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700500 Title: lxc-net incompatible with systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1700500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750654] Re: "lxc-create -B best" fails on non-btrfs/zfs system
** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750654 Title: "lxc-create -B best" fails on non-btrfs/zfs system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713726] Re: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8
** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713726 Title: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758168] Re: [16.04] checkconfig: Warning: new{u, g}idmap is not setuid-root
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758168
Title:
[16.04] checkconfig: Warning: new{u,g}idmap is not setuid-root
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758168/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757229] Re: Oracle containers will fail to start because of missing /usr/lib/x86_64-linux-gnu/lxc/dev
Our pre-generated oracle images are tested daily and seem to be working fine. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757229 Title: Oracle containers will fail to start because of missing /usr/lib/x86_64-linux-gnu/lxc/dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1757229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776214] Re: please package lxc 2.1.1 for xenial updates
We only package LTS releases in Ubuntu. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776214 Title: please package lxc 2.1.1 for xenial updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1776214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715537] Re: package lxc1 2.0.8-0ubuntu1~16.04.2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Error was visible in the log, address/port already in use. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715537 Title: package lxc1 2.0.8-0ubuntu1~16.04.2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1715537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625235] Re: lxc doesn't follow xdg basedir spec if XDG_DATA_HOME is set
** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625235 Title: lxc doesn't follow xdg basedir spec if XDG_DATA_HOME is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1625235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699903] Re: lxc-sshd won't start with 2.0.8
** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699903 Title: lxc-sshd won't start with 2.0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673687] Re: lx-ls crashes and dumps core
** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673687 Title: lx-ls crashes and dumps core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1673687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699592] Re: lxc-create fails for debian jessie armhf
We don't use those template scripts anymore and foreign architecture was never really supported in the first place (and indeed inconsistently between templates). ** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699592 Title: lxc-create fails for debian jessie armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699919] Re: lxc copy between hosts preserves original uid/gid
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699919 Title: lxc copy between hosts preserves original uid/gid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594751] Re: lxc-ls doesn't show nested containers when using an alternate lxc path
** Changed in: lxc (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594751 Title: lxc-ls doesn't show nested containers when using an alternate lxc path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1594751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1607096] Re: lxc-container-default-with-mounting profile systemd permission denied
report matches a setup for 16.04 with upstart instead of systemd and no cgroup-lite or similar pre-mounting the right cgroup, error is correct, host setup is likely the issue. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607096 Title: lxc-container-default-with-mounting profile systemd permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1607096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614232] Re: python-lxc attach_wait prevents further keyboard input
Is that still a thing on 3.x or higher? ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614232 Title: python-lxc attach_wait prevents further keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1614232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619238] Re: #cloud-config in user.user-data not running without ip
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619238 Title: #cloud-config in user.user-data not running without ip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1619238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532069] Re: Can't create a container with a loop backing store in 1.0.8
** Changed in: lxc (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532069 Title: Can't create a container with a loop backing store in 1.0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1532069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620774] Re: lxc container does not start: cgroupfs failed to detect cgroup metadata
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620774 Title: lxc container does not start: cgroupfs failed to detect cgroup metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1620774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302053] Re: lxc-start with bad container name gives strange err message
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302053 Title: lxc-start with bad container name gives strange err message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1302053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556931] Re: lxc: adt testing failing across the board on ppc64el
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556931 Title: lxc: adt testing failing across the board on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549391] Re: /proc/sched_debug Information Leak
So options here are to apparmor block it, assuming that no common piece of software relies on it or to mask it with lxcfs (though that still allows access to user, so not necessarily ideal). I'm a bit confused as to why this data is accessible to unprivileged users in the first place, wouldn't that also allow bypassing some of the /proc filtering modes? ** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549391 Title: /proc/sched_debug Information Leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674679] Re: lxc autopkgtest fails if http_proxy not set
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674679 Title: lxc autopkgtest fails if http_proxy not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1674679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751780] Re: lxc-snapshot crashes when removing non-existing snapshot
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751780 Title: lxc-snapshot crashes when removing non-existing snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1751780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713674] Re: Starting Xenial lxc without cap_sysadmin fails
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713674 Title: Starting Xenial lxc without cap_sysadmin fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684481] Re: KVM guest execution start apparmor blocks on /dev/ptmx now (regression?)
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684481 Title: KVM guest execution start apparmor blocks on /dev/ptmx now (regression?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1684481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758380] Re: unpriveleged containers no longer could start due to start.c: lxc_spawn: 1555 Failed initializing cgroup support
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758380 Title: unpriveleged containers no longer could start due to start.c: lxc_spawn: 1555 Failed initializing cgroup support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556110] Re: package lxc (not installed) failed to install/upgrade: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556110 Title: package lxc (not installed) failed to install/upgrade: 子程序 已安裝的 post- installation script 傳回了錯誤退出狀態 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594751] Re: lxc-ls doesn't show nested containers when using an alternate lxc path
Is that still an issue with the modern lxc-ls (3.x or higher)? ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594751 Title: lxc-ls doesn't show nested containers when using an alternate lxc path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1594751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1527374] Re: CVE-2015-8709
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1527374 Title: CVE-2015-8709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511197] Re: PCI Device Access Through /proc/
** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511197 Title: PCI Device Access Through /proc/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586608] Re: Can not start nested trusty container inside trusty container
trusty is EOL, cgmanager/cgproxy are dead and nesting works way better now thanks to cgroup namespaces. ** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586608 Title: Can not start nested trusty container inside trusty container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1586608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590547] Re: LXC package for trusty no longer has configuration files
** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1472929] Re: undefined symbol: cgmanager_get_pid_cgroup_abs_sync
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472929 Title: undefined symbol: cgmanager_get_pid_cgroup_abs_sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1472929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548497] Re: Cross-Container ARP Poisoning
As LXC doesn't directly manage bridges, we don't expect to do anything there, instead you can use network up/down hooks to manually setup filtering. LXD which does manage networks has support for ipv4, ipv6 and mac filtering on container interfaces. ** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548497 Title: Cross-Container ARP Poisoning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1548497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521151] Re: init: lxc-instance main process terminated with status 255
trusty is EOL and upstart is unsupported at this time. ** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521151 Title: init: lxc-instance main process terminated with status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1521151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537939] Re: apparmor profile for /var/lib/lxd denies mount operation on container creation
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537939 Title: apparmor profile for /var/lib/lxd denies mount operation on container creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1537939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537689] Re: ubuntu template fro lxc messes up proxies
We don't ship those templates anymore, instead relying on pre-made images which will not have any proxy set in them. ** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537689 Title: ubuntu template fro lxc messes up proxies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1537689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1542438] Re: Python LXC api needs to be much better at error reporting
** Changed in: lxc (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1542438 Title: Python LXC api needs to be much better at error reporting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1542438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1359224] Re: Feature request: Add support for multiple bridges
** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1359224 Title: Feature request: Add support for multiple bridges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1359224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544157] Re: lxc exec not working in xenial
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544157 Title: lxc exec not working in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1544157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533244] Re: lxc-net thinks it's already running after it failed
Can someone check if that's still the case on something recent (3.x or 4.x)? ** Changed in: lxc (Ubuntu) Status: New => Incomplete ** Changed in: lxc (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533244 Title: lxc-net thinks it's already running after it failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532069] Re: Can't create a container with a loop backing store in 1.0.8
Has anyone seen this on something recent? Say LXC 3.x or 4.x? ** Changed in: lxc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532069 Title: Can't create a container with a loop backing store in 1.0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1532069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445539] Re: Can't create vivid lxc on trusty
We're now relying on lxc-download which doesn't have such problems. A backported version of lxc in trusty will work fine, though trusty is eol now. ** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445539 Title: Can't create vivid lxc on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1445539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436722] Re: lxc domain setup instructions are incorrect
** Changed in: lxc (Ubuntu) Status: New => Triaged ** Changed in: lxc (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436722 Title: lxc domain setup instructions are incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441307] Re: lxc-clone makes new copies of each hardlinked file
Looking at the current LXC code, "-H" is part of our rsync flags now. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441307 Title: lxc-clone makes new copies of each hardlinked file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
