[Touch-packages] [Bug 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1819572 Title: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction Status in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Bug description: Hardware: Dell Vostro 5568 (CID 201606-22344) [Steps To Reproduce] 1. Install cosmic on this machine 2. Connect to the internet with ethernet 3. do-release-upgrade [Expected Result] Upgrade completes. The wired connection is ready to access the internet. [Actual Result] - The ethernet interface has an IP address assigned by the associated DHCP (checked by "ip -a") - "ping 8.8.8.8" will get "Destination Host Unreachable" [More Information] I tried the same steps on different machine-distro matrix[1] and could only reproduce the issue on this machine. [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco --- [Logs] - /var/log tarball of the system: the attachment 201606-22344-network- manager-nplusone-190312.var-log.tar.gz - Collected by "ubuntu-bug network-manager": /media/tai271828/certsd/201606-22344-network-manager- nplusone-190312.ubuntu.bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1819572 Title: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction Status in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Bug description: Hardware: Dell Vostro 5568 (CID 201606-22344) [Steps To Reproduce] 1. Install cosmic on this machine 2. Connect to the internet with ethernet 3. do-release-upgrade [Expected Result] Upgrade completes. The wired connection is ready to access the internet. [Actual Result] - The ethernet interface has an IP address assigned by the associated DHCP (checked by "ip -a") - "ping 8.8.8.8" will get "Destination Host Unreachable" [More Information] I tried the same steps on different machine-distro matrix[1] and could only reproduce the issue on this machine. [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco --- [Logs] - /var/log tarball of the system: the attachment 201606-22344-network- manager-nplusone-190312.var-log.tar.gz - Collected by "ubuntu-bug network-manager": /media/tai271828/certsd/201606-22344-network-manager- nplusone-190312.ubuntu.bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1575757 Title: Can't install kernel-nfs-server inside lxc container Status in lxc package in Ubuntu: Invalid Bug description: I'm trying to virtualize a package that depends on NFS by installing it in an LXC container. The commands sudo apt-get install nfs-kernel-server sudo lxc-create -n nfstest -t download -- -d ubuntu -r xenial -a amd64 sudo lxc-start -n nfstest sudo lxc-attach -n nfstest apt-get update sudo lxc-attach -n nfstest apt-get install nfs-kernel-server should install NFS server software inside the container, but instead fail with ... Not creating home directory `/var/lib/nfs'. nfs-utils.service is a disabled or a static unit, not starting it. Setting up nfs-kernel-server (1:1.2.8-9ubuntu12) ... A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. nfs-server.service couldn't start. Creating config file /etc/exports with new version Creating config file /etc/default/nfs-kernel-server with new version A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. invoke-rc.d: initscript nfs-kernel-server, action "start" failed. dpkg: error processing package nfs-kernel-server (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... Errors were encountered while processing: nfs-kernel-server E: Sub-process /usr/bin/dpkg returned an error code (1) sudo lxc-attach -n nfstest journalctl -xe reports: Apr 27 15:42:59 nfstest systemd[1]: Failed to mount NFSD configuration filesystem -- Subject: Unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Unit proc-fs-nfsd.mount has failed. -- The result is failed. Presumably this is intended, and there is a way to configure lxc to allow running nfs servers inside it (there are rumors of success on the web), but https://help.ubuntu.com/lts/serverguide/lxc.html is silent on the issue, and doesn't even mention the word nfs. Likewise, https://help.ubuntu.com/lts/serverguide/network-file-system.html doesn't even mention lxc. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 27 08:19:41 2016 InstallationDate: Installed on 2016-03-26 (32 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1575757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389954 Title: Make .lxc domain name resolution easier to discover and enable Status in lxc package in Ubuntu: Triaged Bug description: The lxc package on ubuntu does almost nothing to help a user enable DNS resolution for containers via dnsmaq, let alone discover that it is possible. How about enabling it by default? I think all it would take is adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dnsmasq.d/ and uncommenting LXC_DOMAIN="lxc" in /etc/default/lxc-net. Even if there's a good reason not to enable this by default, shouldn't it at least be clearly documented someplace obvious instead of buried in a system config file with a misleading comment that mentions the wrong dnsmasq file to edit? (The one currently mentioned by /etc/default/lxc-net does nothing on ubuntu desktop systems, because ubuntu's NetworkManager starts dnsmasq with a special config directory.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1569679 Title: lxc failed to do lxc-checkpoint again Status in lxc package in Ubuntu: Invalid Bug description: When doing lxc-checkpoint, it replies: lxc-checkpoint: criu.c: do_dump: 879 dump failed with 1 Checkpointing xxx failed. About my ENV: # uname -a Linux ubuntu 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a Distributor ID: Ubuntu Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 Codename: xenial # apt-cache policy lxc lxc: Installed: 2.0.0-0ubuntu1 Candidate: 2.0.0-0ubuntu1 Version table: *** 2.0.0-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy criu criu: Installed: 2.0-2ubuntu3 Candidate: 2.0-2ubuntu3 Version table: *** 2.0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 12:44:20 2016 PackageArchitecture: all ProcEnviron: LANGUAGE=zh_CN:zh TERM=xterm-256color PATH=(custom, no user) LANG=zh_CN.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1569679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1240757 Title: Bridge not created if bind9 is on Status in bind9 package in Ubuntu: Triaged Status in lxc package in Ubuntu: Won't Fix Status in lxd package in Ubuntu: Won't Fix Bug description: LXC will not create the lxcbr0 bridge if bind9 is on, as it can not take the 10.0.3.1 address. If bind9 is stopped, then LXC successfully creates the bridge. Expected result: LXC will create the bridge, even if bind9 is on. --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 DistroRelease: Ubuntu 13.04 InstallationDate: Installed on 2013-06-29 (110 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True Package: lxc PackageArchitecture: i386 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=4c07e19b-cf33-4cbd-ab6d-fe300398b22b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: bind9utils 1:9.9.2.dfsg.P1-2ubuntu2.1 apparmor 2.8.0-0ubuntu11 Tags: raring Uname: Linux 3.8.0-31-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo modified.conffile..etc.bind.named.conf.local: [modified] mtime.conffile..etc.bind.named.conf.local: 2013-08-01T12:03:20.742316 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1240757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1861880 Title: lxc-attach command does not return error exit code if the command is failed Status in lxc package in Ubuntu: Fix Committed Status in lxc package in Debian: Fix Released Bug description: lxc-attach command does not return error exit code if the command is failed on Ubuntu Focal : root@scribe:~# lxc-start --version 3.0.4 root@scribe:~# lxc-attach --logpriority=DEBUG --name=addc -- exit lxc-attach: addc: attach.c: lxc_attach_run_command: 1489 No such file or directory - Failed to exec "exit" root@scribe:~# echo $? 0 The problem is fixed upstream : https://github.com/lxc/lxc/issues/3104 and by Debian : https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=934983 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lxc-utils 3.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 16:01:30 2020 InstallationDate: Installed on 2020-01-10 (25 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200105) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc-net.default: USE_LXC_BRIDGE="true" LXC_BRIDGE="br0" LXC_ADDR="192.0.2.1" LXC_NETMASK="255.255.255.0" LXC_NETWORK="192.0.2.0/24" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1861880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1858799 Title: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 Status in lxc package in Ubuntu: Fix Committed Status in lxc source package in Bionic: New Bug description: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local diversion of /usr/bin/dirmngr to /usr/bin/dirmngr.orig' SUMMARY: pass=39, fail=1, ignored=1 autopkgtest [20:47:46]: test exercise: ---] autopkgtest [20:47:48]: test exercise: - - - - - - - - - - results - - - - - - - - - - exercise FAIL non-zero exit status 1 autopkgtest [20:47:49]: summary exercise FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1858799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1760848 Title: lxc-create can't create bionic container on xenial Status in lxc package in Ubuntu: Fix Released Bug description: I did run: lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic which fails in the end: (...) Download complete Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ... Generating locales (this might take a while)... de_DE.UTF-8... done Generation complete. mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' nicht möglich: Datei oder Verzeichnis nicht gefunden lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for ubu18.04 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04 I've seen that when creating a xenial container this is the point where new sshd keys get created. dpkg -l 'lxc*' ||/ Name Version +++-==-==- ii lxc2.0.8-0ubuntu1~16.04.2 ii lxc-common 2.0.8-0ubuntu1~16.04.2 ii lxc-templates 2.0.8-0ubuntu1~16.04.2 ii lxc1 2.0.8-0ubuntu1~16.04.2 ii lxcfs 2.0.8-0ubuntu1~16.04.2 un lxcguest un lxctl lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1866124
Title:
ps -eo lxc no longer shows a task's lxc container
Status in lxc package in Ubuntu:
Invalid
Status in procps package in Ubuntu:
New
Bug description:
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc
container within which a task is running. If a process is not running
inside a container, a dash ('-') will be shown." [1]
This worked fine until I upgraded from ubuntu 19.04 to 19.10, which
brought me from lxc 3.03 to 3.04. Now, that column always contains a
dash instead of the container name, even for processes that are
running inside a container. The "lxc" format specifier seems to be
broken now.
[1]
https://manpages.ubuntu.com/manpages/eoan/man1/ps.1.html#standard%20format%20specifiers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1866124/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1659590 Title: containers won't start after lxc and apparmor upgrades in trusty Status in lxc package in Ubuntu: Incomplete Bug description: On January 19 lxc and apparmor were upgraded on our VPN servers: 2017-01-19 06:30:36 upgrade libdbus-1-3:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5 2017-01-19 06:30:37 upgrade python3-lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:38 upgrade libapparmor1:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:38 upgrade libapparmor-perl:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:38 upgrade apparmor:amd64 2.8.95~2430-0ubuntu5.3 2.10.95-0ubuntu2.5~14.04.1 2017-01-19 06:30:39 upgrade lxc-templates:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:40 upgrade liblxc1:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:40 upgrade lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2 2017-01-19 06:30:41 upgrade libseccomp2:amd64 2.1.0+dfsg-1 2.1.1-1ubuntu1~trusty3 2017-01-19 06:30:42 upgrade dbus:amd64 1.6.18-0ubuntu4.4 1.6.18-0ubuntu4.5 The day after, the servers were rebooted and the application containers running the OpenVPN instances failed to start: + lxc-execute -n network-vpn -f /server/network.vpn/lxc/lxc.conf -- /server/network.vpn/lxc/lxc-start.sh lxc-execute: utils.c: safe_mount: 1391 No such file or directory - Failed to mount proc onto /proc lxc-execute: conf.c: tmp_proc_mount: 4132 No such file or directory - failed to mount /proc in the container. lxc-execute: lsm/apparmor.c: apparmor_process_label_get: 80 No such file or directory - opening /proc/1/attr/current lxc-execute: lsm/apparmor.c: apparmor_process_label_set: 191 No such file or directory - failed to change apparmor profile to lxc-container-default lxc-execute: sync.c: __sync_wait: 57 An error occurred in another process (expected sequence number 5) lxc-execute: start.c: __lxc_start: 1149 failed to spawn 'network-vpn' lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing hugetlb:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing perf_event:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing blkio:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing freezer:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing devices:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing memory:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing name=systemd:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpuacct:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpu:lxc/network-vpn lxc-execute: cgmanager.c: cgm_remove_cgroup: 523 call to cgmanager_remove_sync failed: invalid request lxc-execute: cgmanager.c: cgm_remove_cgroup: 525 Error removing cpuset:lxc/network-vpn We had to downgrade lxc, apparmor and related packages to the latest version from trusty-security instead of trusty-updates to get the VPN up and running again. Details: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.5 LTS Release: 14.04 Codename: trusty 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Any clue about what's going on? Thanks, Alex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in ubuntu-kernel-tests: Confirmed Status in lxc package in Ubuntu: Invalid Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1776381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1843383 Title: lxc, please bump epoch to 1 Status in lxc package in Ubuntu: New Bug description: A lot of stuff from Debian is bd-uninstallable because of the missing epoch on the Ubuntu package. e.g. lua-lxc, and general packages using liblxc1 at runtime (python3-lxc and something else). I think bumping epoch (whilst bad in general), would be a big improvement in this case (also MergeOMatic will stop being unhelpful with lxc merges) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1843383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1794523 Title: lxc-net.service is not properly ordered with network-online.target Status in lxc package in Ubuntu: Incomplete Bug description: I made several tests and I figure out that the lxc-net.service is missing a Wants= directive to be properly ordered against network- online.target. As I understand the systemd.unit manpage, to be properly ordered a unit must define a Requires=/Wants= in addition to an After=/Before=. Regards. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1794523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1840639 Title: Version 3.0.3 breaks lxc-usernsexec Status in lxc package in Ubuntu: Incomplete Bug description: Affected version: 3.0.3 Last working version: 3.0.1 Upgrade from 3.0.1 to 3.0.3 for lxc packages breaks lxc-usernsexec with message 'Failed to find subuid or subgid allocation' even those allocation is fine. Downgrading back to 3.0.1 fixes the problem. Steps to reproduce: Set up 3.0.1 lxc to work. (lxc-usernsexec whoami should show 'root') Upgrade to 3.0.3 Run lxc-usernsexec whoami Expected result: root Actual result: Failed to find subuid or subgid allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1840639/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1828255
Title:
It's too easy to accidentally delete a container rather than a
snapshot
Status in lxc package in Ubuntu:
Fix Released
Bug description:
The command to delete a container is:
lxc delete {container}/{snapshot}
Unfortunately, if the "/" is omitted, this command deletes {container}
without any sort of prompting. It would be very helpful to add a
prompt/verification when deleting the entire container to avoid
mishaps. Don't ask me how I know that they happen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1828255/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1837537 Title: FTBFS since lxc has different version numbers in Debian and Ubuntu Status in lua-lxc package in Ubuntu: Fix Committed Status in lxc package in Ubuntu: In Progress Bug description: The lua-lxc [1] package currently fails to build since it cannot satisfy the build dependency: lxc-dev (>= 1:3.0.2-1~exp+1). Looks like this is caused by different version numbers in Debian and Ubuntu. The latest version in Debian unstable is 1:3.1.0+really3.0.3-8 while Ubuntu eoan has 3.0.3-0ubuntu1. I believe the 1: epoch (?) is causing this issue. Presumably lua-lxc needs to be patched to allow the Ubuntu package to fulfill the build requirements. [1] https://bugs.launchpad.net/ubuntu/+source/lua-lxc/1:3.0.2-1 [2] https://bugs.launchpad.net/ubuntu/+source/lua-lxc/1:3.0.2-1/+build/16664061 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lxc/+bug/1837537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1787436 Title: lxc 3.0.1-0ubuntu2 ADT test failure with linux 4.18.0-5.6 Status in lxc package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/amd64/l/lxc/20180816_134239_340a6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/arm64/l/lxc/20180816_135423_340a6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/l/lxc/20180816_134641_340a6@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/ppc64el/l/lxc/20180816_134231_340a6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/s390x/l/lxc/20180816_134140_340a6@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1787436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1857046 Title: lxc 3.0.4-0ubuntu2 ADT test failure with linux 5.5.0-2.3 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/amd64/l/lxc/20191218_145013_76e0c@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/arm64/l/lxc/20191218_165648_a3f34@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/ppc64el/l/lxc/20191218_151902_0998c@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-canonical-kernel-team-bootstrap/focal/s390x/l/lxc/20191218_152251_9101b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1857046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1508744 Title: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade Status in Release Notes for Ubuntu: New Bug description: With lxc installed, the 15.04 -> 15.10 upgrade fails. The upgrade completes if LXC is removed and then reinstalled later. Here is me using apt to try and make it work (gives same errors as upgrade- manager did): Setting up lxc (1.1.4-0ubuntu1) ... Job for lxc-net.service failed because the control process exited with error code. See "systemctl status lxc-net.service" and "journalctl -xe" for details. invoke-rc.d: initscript lxc-net, action "start" failed. dpkg: error processing package lxc (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of lxc-templates: lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however: Package lxc is not configured yet. dpkg: error processing package lxc-templates (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: lxc lxc-templates E: Sub-process /usr/bin/dpkg returned an error code (1) ╭─michael@michael-desktop-ubuntu ~ ‹› ╰─$ systemctl status lxc-net.service 100 ↵ ● lxc-net.service - LXC network bridge setup Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2015-10-22 12:50:07 AEDT; 27s ago Process: 22655 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-net start (code=exited, status=1/FAILURE) Main PID: 22655 (code=exited, status=1/FAILURE) Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: Starting LXC network bridge setup... Oct 22 12:50:07 michael-desktop-ubuntu lxc-net[22655]: lxc-net is already running Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Main process exited, code=exited, status=1/FAILURE Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: Failed to start LXC network bridge setup. Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Unit entered failed state. Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1758168
Title:
[16.04] checkconfig: Warning: new{u,g}idmap is not setuid-root
Status in lxc package in Ubuntu:
Fix Released
Bug description:
Hit this again today on 16.04 on a new system. Thought I'd reported
this but obviously not.
lxc-checkconfig erroneously reports:
Kernel configuration not found at /proc/config.gz; searching...
Kernel configuration found at /boot/config-4.13.0-37-lowlatency
--- Namespaces ---
Namespaces: enabled
Utsname namespace: enabled
Ipc namespace: enabled
Pid namespace: enabled
User namespace: enabled
Warning: newuidmap is not setuid-root
Warning: newgidmap is not setuid-root
Network namespace: enabled
...
17.10+ have the corrected version; it would be useful to get into
16.04.
--- a/src/tools/lxc-checkconfig.in2017-06-14 21:15:23.0 +0100
+++ b/src/tools/lxc-checkconfig.in2017-10-11 21:52:12.609283395 +0100
@@ -89,16 +91,16 @@
echo -n "Pid namespace: " && is_enabled CONFIG_PID_NS yes
echo -n "User namespace: " && is_enabled CONFIG_USER_NS
if is_set CONFIG_USER_NS; then
- if type newuidmap > /dev/null 2>&1; then
- f=`type -P newuidmap`
+ if which newuidmap > /dev/null 2>&1; then
+ f=`which newuidmap`
if [ ! -u "${f}" ]; then
echo "Warning: newuidmap is not setuid-root"
fi
else
echo "newuidmap is not installed"
fi
- if type newgidmap > /dev/null 2>&1; then
- f=`type -P newgidmap`
+ if which newgidmap > /dev/null 2>&1; then
+ f=`which newgidmap`
if [ ! -u "${f}" ]; then
echo "Warning: newgidmap is not setuid-root"
fi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758168/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1776214 Title: please package lxc 2.1.1 for xenial updates Status in lxc package in Ubuntu: Invalid Bug description: Please package lxc 2.1.1 for xenial updates as this will fix some bugs, i.e. fixing creation of bionic containers #1760848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1776214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in 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 Status in lxc package in Ubuntu: Fix Released Bug description: How to produce? 1. On a latest Ubuntu 17.10 2. Install lxc1 (2.1.0 here) 3. Run as root: lxc-create --name=OracleLinux7 --template=oracle -- --arch=x86_64 --release=7.latest --rootfs=/mnt/disks/hgst/part_3/var/storage//lxc-images/OracleLinux7 4. Run as root: lxc-start --name=OracleLinux7 What actually happens? lxc-start: OracleLinux7: lxccontainer.c: wait_on_daemonized_start: 760 Received container state "ABORTING" instead of "RUNNING" lxc-start: OracleLinux7: tools/lxc_start.c: main: 368 The container failed to start. lxc-start: OracleLinux7: tools/lxc_start.c: main: 370 To get more details, run the container in foreground mode. lxc-start: OracleLinux7: tools/lxc_start.c: main: 372 Additional information can be obtained by setting the --logfile and --logpriority options. What should happen? Return nothing and start normally Additional information: lxc-start OracleLinux7 20180320175430.833 ERRORlxc_conf - conf.c:lxc_setup_ttydir_console:1621 - No such file or directory - failed with errno 2 to create /usr/lib/x86_64-linux-gnu/lxc/dev/lxc lxc-start OracleLinux7 20180320175430.833 ERRORlxc_conf - conf.c:lxc_setup:3226 - Failed to setup console lxc-start OracleLinux7 20180320175430.833 ERRORlxc_start - start.c:do_start:921 - Failed to setup container "OracleLinux7". lxc-start OracleLinux7 20180320175430.833 ERRORlxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 5) lxc-start OracleLinux7 20180320175430.892 ERRORlxc_container - lxccontainer.c:wait_on_daemonized_start:760 - Received container state "ABORTING" instead of "RUNNING" lxc-start OracleLinux7 20180320175430.892 ERRORlxc_start - start.c:__lxc_start:1451 - Failed to spawn container "OracleLinux7". lxc-start OracleLinux7 20180320175430.892 ERRORlxc_start_ui - tools/lxc_start.c:main:368 - The container failed to start. lxc-start OracleLinux7 20180320175430.892 ERRORlxc_start_ui - tools/lxc_start.c:main:370 - To get more details, run the container in foreground mode. lxc-start OracleLinux7 20180320175430.892 ERRORlxc_start_ui - tools/lxc_start.c:main:372 - Additional information can be obtained by setting the --logfile and --logpriority options. When I review the differences between /usr/share/lxc/config/debian.common.conf and /usr/share/lxc/config/oracle.common.conf. The following parameters are omitted from /usr/share/lxc/config/oracle.common.conf: # This derives from the global common config lxc.include = /usr/share/lxc/config/common.conf # Doesn't support consoles in /dev/lxc/ lxc.tty.dir = The following is set in /usr/share/lxc/config/common.conf: # Setup the LXC devices in /dev/lxc/ lxc.tty.dir = lxc ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lxc1 2.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 20 14:22:10 2018 InstallationDate: Installed on 2017-12-26 (84 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = br1 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: Mar 20 12:28:40 budgie-desktop libvirtd[2563]: 2018-03-20 16:28:40.861+: 2591: error : lxcDomainUndefineFlags:534 : unsupported flags (0x3) in function lxcDomainUndefineFlags modified.conffile..etc.lxc.default.conf: lxc.net.0.type = veth lxc.net.0.link = br1 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx mtime.conffile..etc.lxc.default.conf: 2018-03-20T12:45:32.850543 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1757229/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1750654 Title: "lxc-create -B best" fails on non-btrfs/zfs system Status in lxc package in Ubuntu: Fix Released Bug description: As per documentation, the `-B best` option should automatically select the best backingstore, falling back all the way to dir. But apparently it doesn't, at least not in artful's 2.1.0-0ubuntu1: $ sudo lxc-create -B best --name=autopkgtest-xenial -t ubuntu -- -r xenial lxc-create: autopkgtest-xenial: storage/btrfs.c: btrfs_create: 860 Inappropriate ioctl for device - Failed to create btrfs subvolume "/var/lib/lxc/autopkgtest-xenial/rootfs" lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_create: 758 Failed to create zfs dataset "zfs:lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial: utils.c: run_command: 2326 failed to exec command lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_mount: 256 No such file or directory - Failed to mount "lxc/autopkgtest-xenial" on "/usr/lib/x86_64-linux-gnu/lxc" lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1294 Failed to mount rootfs lxc-create: autopkgtest-xenial: lxccontainer.c: create_run_template: 1473 container creation template for autopkgtest-xenial failed lxc-create: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to detect zfs dataset "lxc/autopkgtest-xenial": lxc-create: autopkgtest-xenial: lxc-create: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error destroying rootfs for autopkgtest-xenial lxc-create: autopkgtest-xenial: tools/lxc_create.c: main: 326 Error creating container autopkgtest-xenial Moreover, it creates cruft which is hard to clean up again: $ sudo lxc-ls -f NAME STATE AUTOSTART GROUPS IPV4 IPV6 autopkgtest-xenial STOPPED 0 - -- $ sudo lxc-destroy -n autopkgtest-xenial lxc-destroy: autopkgtest-xenial: storage/zfs.c: zfs_destroy: 613 Failed to detect zfs dataset "lxc/autopkgtest-xenial": lxc-destroy: autopkgtest-xenial: utils.c: run_command: 2326 failed to exec command lxc-destroy: autopkgtest-xenial: lxccontainer.c: container_destroy: 2653 Error destroying rootfs for autopkgtest-xenial Destroying autopkgtest-xenial failed $ sudo ls -lR /var/lib/lxc/autopkgtest-xenial /var/lib/lxc/autopkgtest-xenial: total 8 -rw-r--r-- 1 root root 149 Feb 20 20:41 config drwxr-xr-x 2 root root 4096 Feb 20 20:41 rootfs /var/lib/lxc/autopkgtest-xenial/rootfs: total 0 This can only be cleaned up with `sudo rm -r`. autopkgtest-build-lxc uses this option to get performant containers out of the box. Arguably `-B best` is a sort of "unbreak my containers" option and should always implicitly be used, but is there something else that I should do here? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lxc 2.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Feb 20 20:38:55 2018 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1750654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1713726 Title: lxc 2.0.8-0ubuntu6 ADT test failure with linux 4.13.0-7.8 Status in lxc package in Ubuntu: Fix Released Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/amd64/l/lxc/20170829_024349_c4b5f@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/i386/l/lxc/20170829_025427_c4b5f@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/l/lxc/20170829_024824_c4b5f@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1700500 Title: lxc-net incompatible with systemd-resolved Status in lxc package in Ubuntu: Triaged Bug description: Symptoms If an lxc container named *mycontainer* runs, it is not accessible using name *mycontainer.lxc*. Causes -- The lxc1 package provides the lxc-net.service which launch a dns-masq process to act as dns providing name resolution to local lxc instances using the .lxc domain. This DNS is however not declared to systemd-resolved, and so .lxc names do not work on a standard ubuntu install. Proposed solution - The lxc1 package should provide a /etc/systemd/resolved.conf.d/lxc.conf with the following content:: [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lxc1 2.0.8-0ubuntu1~17.04.2 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 26 11:07:24 2017 InstallationDate: Installed on 2015-11-10 (593 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: lxc UpgradeStatus: Upgraded to zesty on 2017-02-25 (120 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1700500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1715537 Title: package lxc1 2.0.8-0ubuntu1~16.04.2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in lxc package in Ubuntu: Invalid Bug description: - ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lxc1 2.0.8-0ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Sep 1 07:45:15 2017 DpkgHistoryLog: Start-Date: 2017-09-01 07:42:07 Requested-By: chtcherba (1000) Install: lxctl:amd64 (0.3.1+debian-3, automatic), liblinux-lvm-perl:amd64 (0.17-2, automatic), python3-lxc:amd64 (2.0.8-0ubuntu1~16.04.2, automatic), lxc-templates:amd64 (2.0.8-0ubuntu1~16.04.2, automatic), lxc1:amd64 (2.0.8-0ubuntu1~16.04.2, automatic), redir:amd64 (2.2.1-13, automatic), lxc:amd64 (2.0.8-0ubuntu1~16.04.2, automatic), cloud-image-utils:amd64 (0.27-0ubuntu24, automatic), vagrant-lxc:amd64 (1.2.1-2), python-requestbuilder:amd64 (0.2.3-1, automatic), libpam-cgfs:amd64 (2.0.7-0ubuntu1~16.04.2, automatic), euca2ools:amd64 (3.1.0-1, automatic), vagrant-cachier:amd64 (1.2.1-2), cloud-utils-euca:amd64 (0.27-0ubuntu24, automatic), libnet-ssh2-perl:amd64 (0.58-3, automatic) ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-03-29 (526 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) KernLog: ProcCmdline: BOOT_IMAGE=/vmlinuz-4.11.0-14-generic root=/dev/mapper/hostname-root ro nomdmonddf nomdmonisw selinux=1 enforcing=0 fsck.repair=yes SourcePackage: lxc Title: package lxc1 2.0.8-0ubuntu1~16.04.2 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to xenial on 2016-05-12 (482 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1715537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1625235 Title: lxc doesn't follow xdg basedir spec if XDG_DATA_HOME is set Status in lxc package in Ubuntu: Triaged Bug description: Pretty simple bug: lxc-create: utils.c: mkdir_p: 253 Permission denied - failed to create directory '/home/desrt/.local/share/lxc' desrt@humber:~$ echo $XDG_DATA_HOME /home/desrt/.var/lib lxc has no business putting files in ~/.local/share if XDG_DATA_HOME is set elsewhere. Please see https://standards.freedesktop.org /basedir-spec/basedir-spec-latest.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1625235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1673687 Title: lx-ls crashes and dumps core Status in lxc package in Ubuntu: Fix Released Bug description: See https://github.com/lxc/lxc/issues/1466 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.9-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39 Uname: Linux 3.13.0-110-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Fri Mar 17 08:06:13 2017 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1673687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699903 Title: lxc-sshd won't start with 2.0.8 Status in lxc package in Ubuntu: Fix Released Bug description: On a xenial system after an update to lxc, starting a container created with the lxc-sshd template fails consistently. This does not occur with 2.0.7. root@xenial:~# lxc-create -n mysshd -t /usr/share/lxc/templates/lxc-sshd Generating public/private rsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: SHA256:eR4Kv8JpWxe+RvIudD8LTuOYSGmLdnmX1CgB3Y/IHP4 root@xenial The key's randomart image is: +---[RSA 2048]+ | . . | | . o . | | = o o | |*.. .| | . So+o | | ++=Eo.| | .+++BBo | |.+B+oO=+o| | ..o+++== .o | +[SHA256]-+ Generating public/private dsa key pair. Your identification has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key. Your public key has been saved in /var/lib/lxc/mysshd/rootfs/etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: SHA256:Jmet2LLZMtolKBhfDQ/Za4i3yr0/993umj4Hq0D8Qyg root@xenial The key's randomart image is: +---[DSA 1024]+ | | | o | |+ . | | . * o o | |. . + E S o | | + o + X + .| |. o o + = o o | | . + .+B.. ooo. | | o ++==..oo=*+ | +[SHA256]-+ root@xenial:~# lxc-start -n mysshd --logfile mysshd.log lxc-start: tools/lxc_start.c: main: 366 The container failed to start. lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# cat mysshd.log lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup_dev_console:1473 - Read-only file system - error unlinking /usr/lib/x86_64-linux-gnu/lxc/dev/console lxc-start 20170622214710.829 ERRORlxc_conf - conf.c:lxc_setup:4055 - failed to setup the console for 'mysshd' lxc-start 20170622214710.829 ERRORlxc_start - start.c:do_start:811 - Failed to setup container "mysshd". lxc-start 20170622214710.829 ERRORlxc_sync - sync.c:__sync_wait:57 - An error occurred in another process (expected sequence number 3) lxc-start 20170622214710.868 ERRORlxc_start - start.c:__lxc_start:1358 - Failed to spawn container "mysshd". lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:366 - The container failed to start. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:368 - To get more details, run the container in foreground mode. lxc-start 20170622214715.901 ERRORlxc_start_ui - tools/lxc_start.c:main:370 - Additional information can be obtained by setting the --logfile and --logpriority options. root@xenial:~# dpkg -l '*lxc*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---== un liblxc0 (no description available) ii liblxc12.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (library) ii lxc2.0.8-0ubuntu1~16.04.2 all Transitional package for lxc1 ii lxc-common 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (common tools) ii lxc-templates 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools ii lxcfs 2.0.6-0ubuntu1~16.04.1 amd64 FUSE based filesystem for LXC un lxctl (no description available) ii python3-lxc2.0.8-0ubuntu1~16.04.2 amd64 Linux Containers userspace tools (Python
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699919 Title: lxc copy between hosts preserves original uid/gid Status in lxc package in Ubuntu: Invalid Bug description: I tried to copy an lxc container between two hosts. All worked as expected, but when I looked at the underlying filesystem I realised that the container that has been copied onto the new machine retained its original uid/gid (running unprivileged): root@ii:/var/lib/lxd/containers# ls -al total 24 drwx--x--x 1 root root 58 Jun 23 12:01 . drwxr-xr-x 1 root root182 Jun 23 12:04 .. drwxr-xr-x+ 1 10 10 56 Jun 23 10:38 backend -rw-r--r-- 1 root root 4446 Jun 23 12:04 lxc-monitord.log drwxr-xr-x+ 1 10 10 56 Jun 23 12:01 putils (putils has been copied from a different host). I'd expect a new uid/gid to be allocated for the copied host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699592 Title: lxc-create fails for debian jessie armhf Status in lxc package in Ubuntu: Won't Fix Bug description: I: Extracting zlib1g... W: Failure trying to run: chroot /var/cache/lxc/debian/partial-jessie-armhf mount -t proc proc /proc W: See /var/cache/lxc/debian/partial-jessie-armhf/debootstrap/debootstrap.log for details Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for jessie-armhf failed lxc-create: tools/lxc_create.c: main: 318 Error creating container jessie-armhf root@finfin-ubuntuvm:~# cat /etc/debian_version stretch/sid root@finfin-ubuntuvm:~# do-release-upgrade Checking for a new Ubuntu release No new release found root@finfin-ubuntuvm:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty root@finfin-ubuntuvm:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1699592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1614232
Title:
python-lxc attach_wait prevents further keyboard input
Status in lxc package in Ubuntu:
Incomplete
Bug description:
I previously reported this bug on Github
(https://github.com/lxc/lxc/issues/1137), but am duplicating the
report here for completeness.
I've found that my python scripts stop responding to keyboard input
after running an lxc attach_wait command in python3-lxc
(2.0.4-0ubuntu2).
I wrote a small script to quickly reproduce the issue. With the
script, one can see that using Ctrl+C before running the lxc command
causes a KeyboardInterrupt, but using Ctrl+C after the lxc command
finishes is no longer caught.
#!/usr/bin/env python3
import lxc
import time
import os
CONTAINER_NAME='xenial'
CONTAINER_PATH='%s/.cache/libertine-container' % os.environ["HOME"]
def lxc_work():
container = lxc.Container(CONTAINER_NAME, CONTAINER_PATH)
container.start()
container.attach_wait(lxc.attach_run_command, ['ls'])
print("Ctrl+C will attempt to stop the script during the next ~5 seconds")
time.sleep(5)
print("Running lxc command 'ls' in container '%s', please wait..." %
CONTAINER_NAME)
lxc_work()
print("Ctrl+C should attempt to stop the script in the next ~5 seconds,
but doesn't")
time.sleep(5)
Also see:
https://gist.github.com/larryprice/f562f838ff84929c1619978a6404b8b6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1614232/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1619238 Title: #cloud-config in user.user-data not running without ip Status in lxc package in Ubuntu: Invalid Bug description: I'm having the darndest issue that a cloud config script that is present in a lxc profile and should beapplied on creation is not being run on boot on any image on three different servers when there is no dhcp server or IP present on spun up image. There is nothing in the logs that indicate an error, the process to apply the cloud data just doesn't run. I can see that data read into /var/lib/cloud/seed/nocloud-net/user-data and it's present. But it is not applied unless I manually give the machine an IP address, not before which is quite annoying as I am applying the IP address through the profile in this instance. The logs are no help, they just say it ran successfully when I add an IP address manually or are silent about running cloud-init when it doesn't have one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1619238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1607096 Title: lxc-container-default-with-mounting profile systemd permission denied Status in lxc package in Ubuntu: Invalid Bug description: On a fresh install of Xenial just install lxc. Run typical lxc init setup. lxc-create any Ubuntu version (Trusty/Wily/Xenial tested) container and configure it to use the lxc-container-default-with- mounting. No further configuration needed. Start the container. You will find in dmesg errors concerning problems mounting things in /sys/... [10870.395952] audit: type=1400 audit(1469484639.890:94): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-with-mounting" name="/sys/fs/cgroup/systemd/" pid=14796 comm="systemd" fstype="cgroup" srcname="cgroup" flags="rw, nosuid, nodev, noexec" The container will appear start and you can attach, but its broken. Things like networking won't work. You cannot lxc-stop the container without -k. Starting the container in foreground mode leads to the following error. Failed to mount cgroup at /sys/fs/cgroup/systemd: Permission Denied [!] Failed to mount API fileysystems, freezing. Freezing execution. I found defect https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 concerning Trusty. The issue seems similar but not specially calling out the aa profile. Also, I cannot actually recreate this problem in Trusty. (UPDATE: Forgot to mention I have 2 additional conf lines as follows) lxc.cgroup.devices.allow = b 7:* rwm lxc.cgroup.devices.allow = c 10:237 rwm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1607096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1532069 Title: Can't create a container with a loop backing store in 1.0.8 Status in lxc package in Ubuntu: Incomplete Bug description: Since version 1.0.8 of the lxc package in trusty it appears that it's no longer possible to create a container with a loop backing store. To reproduce the issue, install version 1.0.8-0ubuntu0.3 of the lxc, liblxc1 and python3-lxc packages on trusty and run the following: root@c4b2:/var/lib/lxc# /usr/bin/lxc-create -l DEBUG -n testcontainer --bdev loop -t ubuntu -- -r precise lxc_container: bdev.c: do_loop_create: 2036 Error creating filesystem type ext3 on /var/lib/lxc/testcontainer/rootdev lxc_container: lxccontainer.c: do_bdev_create: 819 Failed to create backing store type loop lxc_container: lxccontainer.c: lxcapi_create: 1299 Error creating backing store type loop for testcontainer lxc_container: lxc_create.c: main: 274 Error creating container testcontainer If I downgrade all the lxc packages to 1.0.7 on the same system it works fine. This issue is similar to what was reported in https://lists.linuxcontainers.org/pipermail/lxc- users/2015-September/010092.html but in that case the issue was occurring when running with backport versions 1.1.3, 1.1.2 but again, not with version 1.0.7. Please let me know if you require further information. Mike. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1532069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1620774 Title: lxc container does not start: cgroupfs failed to detect cgroup metadata Status in lxc package in Ubuntu: Invalid Bug description: lxc container failed to start until after I installed cgroupfs-mount After a recent upgrade, I received the following error messages when start an lxc container: kevin@awabi:~$ sudo lxc-start -F -n escale_build lxc-start: cgroups/cgfs.c: cgfs_init: 2288 cgroupfs failed to detect cgroup metadata lxc-start: start.c: lxc_spawn: 1094 failed initializing cgroup support lxc-start: start.c: __lxc_start: 1354 failed to spawn 'escale_build' lxc-start: tools/lxc_start.c: main: 344 The container failed to start. lxc-start: tools/lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. aptitude install cgroupfs-mount Then I could successful start my container. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.4-0ubuntu1~ubuntu16.04.2 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 11:26:12 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-18 (477 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to xenial on 2016-05-30 (99 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1620774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1594751 Title: lxc-ls doesn't show nested containers when using an alternate lxc path Status in lxc package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 PAckage : dpkg -l|grep lxc ii liblxc1 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (library) ii lxc 2.0.1-0ubuntu1~16.04.1 all Transitional package for lxc1 ii lxc-common 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (common tools) ii lxc-templates2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools ii lxcfs2.0.1-0ubuntu1~16.04.1 amd64 FUSE based filesystem for LXC ii python3-lxc 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (Python 3.x bindings) Same problem than https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177412 If a container path is not the default one, lxc-ls can't give container information, even with -P path/container options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1594751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1556931 Title: lxc: adt testing failing across the board on ppc64el Status in lxc package in Ubuntu: Fix Released Bug description: We are seeing ADT test failures across all kernels on all releases (which have the architecture) on ppc64el. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1302053 Title: lxc-start with bad container name gives strange err message Status in lxc package in Ubuntu: Fix Released Bug description: $ sudo lxc-start -d -n mongodb-server-1 [sudo] password for kapil: lxc-start: Executing '/sbin/init' with no configuration file may crash the host how bout just no such container exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1302053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1549391 Title: /proc/sched_debug Information Leak Status in lxc package in Ubuntu: Triaged Bug description: Description: Unprivileged containers can read from '/proc/sched_debug', a world-readable file within proc that contains a large amount of CFS and CPU scheduler information. This allows a trivial information leak which discloses what processes IDs and names are running in the host or other containers, as well as cgroup information which can disclose container names and other details. This effectively breaks the expected PID Namespace isolation. Reproduction: Inside a default and unprivileged LXC container, run the command `cat /proc/sched_debug`. Note that information is displayed about processes running on the host, as well as inside other containers. Sample output includes: task PID tree-key switches prio exec-runtime sum-exec sum-sleep -- kthreadd 2 319429235.224770 9339 120 319429235.224770 753.267075 1067018909.484918 0 / rcu_sched 7 319489137.064234 18896675 120 319489137.064234 170125.420028 1066508074.968528 0 / rcuos/513 319218638.012762 192 120 319218638.012762 0.896416 1065991450.159691 0 / SNIP SNIP acpid 1813 57932.203222 1676704 120 57932.203222 114395.580999 1067170248.528885 0 /autogroup-222 sh 2273 113050772.15088442 120 113050772.150884 0.754525 1066111947.155906 0 /user/1000.user/c1.session bash 2276 113052316.082339 788 120 113052316.082339 137.826052 1066155735.798643 0 /user/1000.user/c1.session wpa_supplicant 2319 113098971.410443119765 120 113098971.410443 6903.885769 1067229349.942336 0 /user/1000.user/c1.session sh 2426 113050772.15195643 120 113050772.151956 2.035147 1066012436.338286 0 /user/1000.user/c1.session urxvt 2440 113098872.794317606323 120 113098872.794317 28198.224898 1067122648.025421 0 /user/1000.user/c1.session dbus-daemon 2664 113092371.341763 6155 109 113092371.341763 432.939147 1066723733.656385 0 /user/1000.user/c1.session dio/dm-2 2695 20657.783903 2 100 20657.783903 0.007240 0.002253 0 / Chrome_FileThre 3286 31903985.081343213744 120 31903985.081343 14398.389541 1065335604.938435 0 /lxc/chrome Recommendation: In the short term, modify the base LXC AppArmor profile to block access to this file. In the long term, this procfs interface should be rewritten to be namespace aware and possibly restricted to root-only users. If AppArmor is not in use, end-users could recompile their kernel to have CONFIG_SCHED_DEBUG disabled. # About NCC: NCC Group is a security consulting company that performs all manner of security testing and has a strong desire to help make the industry a better, more resilient place. Because of this, when NCC Group identifies vulnerabilities in a system they prefer to work closely with vendors to create more secure systems. NCC Group strongly believes in responsible disclosure, and has strict guidelines in place to ensure that proper disclosure procedure is followed at all times. This serves the dual purpose of allowing the vendor to safely secure the product or system in question as well as allowing NCC Group to share cutting edge research or advisories with the security community. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1684481 Title: KVM guest execution start apparmor blocks on /dev/ptmx now (regression?) Status in apparmor package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Invalid Bug description: Setup: - Xenial host - lxd guests with Trusty, Xenial, ... - add a LXD profile to allow kvm [3] (inspired by stgraber) - spawn KVM guests in the LXD guests using the different distro release versions - guests are based on the uvtool default template which has a serial console [4] Issue: - guest starting with serial device gets blocked by apparmor and killed on creation - This affects at least ppc64el and x86 (s390x has no serial concept that would match) - This appeared in our usual checks on -proposed releases so maybe we can/should stop something? Last good was "Apr 5, 2017 10:40:50 AM" first bad one "Apr 8, 2017 5:11:22 AM" Background: We use this setup for a while and it was working without a change on our end. Also the fact that it still works in the Trusty LXD makes it somewhat suspicious. Therefore I'd assume an SRUed change in LXD/Kernel/Apparmor might be the reason and open this bug to get your opinion on it. You can look into [1] and search for uvt-kvm create in it. Deny in dmesg: [652759.606218] audit: type=1400 audit(1492671353.134:4520): apparmor="DENIED" operation="open" namespace="root//lxd-testkvm-xenial-from_" profile="libvirt-668e21f1-fa55-4a30-b325-0ed5cfd55e5b" name="/dev/pts/ptmx" pid=27162 comm="qemu-system-ppc" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 Qemu-log: 2017-04-20T06:55:53.139450Z qemu-system-ppc64: -chardev pty,id=charserial0: Failed to create PTY: No such file or directory There was a similar issue on qmeu namespacing (which we don't use on any of these releases) [2]. While we surely don't have the "same" issue the debugging on the namespacing might be worth as it could be related. Workaround for now: - drop serial section from guest xml [1]: https://jenkins.ubuntu.com/server/view/Virt/job/virt-migration-cross-release-amd64/78/consoleFull [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1421036 [3]: https://git.launchpad.net/~ubuntu-server/ubuntu/+source/qemu-migration-test/tree/kvm_profile.yaml [4]: https://libvirt.org/formatdomain.html#elementsCharPTY --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: ppc64el DistroRelease: Ubuntu 16.04 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: lxd PackageArchitecture: ppc64el ProcKernelCmdline: root=UUID=902eaad1-2164-4f9a-bec4-7ff3abc15804 ro console=hvc0 ProcLoadAvg: 3.15 3.02 3.83 1/3056 79993 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-72-generic (buildd@bos01-ppc64el-022) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Syslog: Tags: xenial uec-images Uname: Linux 4.4.0-72-generic ppc64le UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: utah _MarkForUpload: True cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT is off --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: ppc64el DistroRelease: Ubuntu 16.04 NonfreeKernelModules: cfg80211 ebtable_broute ebtable_nat binfmt_misc veth nbd openvswitch vhost_net vhost macvtap macvlan xt_conntrack ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables xt_comment xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables zfs zunicode zcommon znvpair spl zavl kvm_hv kvm ipmi_powernv ipmi_msghandler uio_pdrv_genirq vmx_crypto powernv_rng ibmpowernv leds_powernv uio ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure mlx4_en vxlan ip6_udp_tunnel udp_tunnel mlx4_core ipr Package: lxd PackageArchitecture: ppc64el ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdline: root=UUID=902eaad1-2164-4f9a-bec4-7ff3abc15804 ro
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in 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 Status in lxc package in Ubuntu: Fix Released Bug description: After upgrade from xenial to bionic (beta) I no longer could start unpriveleged containers, they failed with following message: lxc-start: test: start.c: lxc_spawn: 1555 Failed initializing cgroup support lxc-start: test: start.c: __lxc_start: 1868 Failed to spawn container "test" The container failed to start. Additional information can be obtained by setting the --logfile and --logpriority options. Moreover, I could see this in auth log: Mar 23 18:21:46 host sudo: PAM unable to dlopen(pam_cgfs.so): /lib/security/pam_cgfs.so: cannot open shared object file: No such file or directory Mar 23 18:21:46 host sudo: PAM adding faulty module: pam_cgfs.so I have installed libpam-cgfs, but it provides only /lib/x86_64-linux- gnu/security/pam_cgfs.so Moreover, if I create a symlink from /lib/security/pam_cgfs.so to /lib/x86_64-linux-gnu/security/pam_cgfs.so it fails with follwing message: PAM unable to dlopen(pam_cgfs.so): /lib/security/pam_cgfs.so: undefined symbol: file_exists ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.0~beta2-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Fri Mar 23 18:20:38 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (274 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1751780 Title: lxc-snapshot crashes when removing non-existing snapshot Status in lxc package in Ubuntu: Fix Released Bug description: Easy to reproduce: # lxc-snapshot --name foo -r snap0 Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lxc1 2.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Feb 26 15:12:20 2018 InstallationDate: Installed on 2017-03-29 (334 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: lxc UpgradeStatus: Upgraded to artful on 2017-12-14 (74 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1751780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1674679
Title:
lxc autopkgtest fails if http_proxy not set
Status in lxc package in Ubuntu:
Fix Released
Bug description:
debian/tests/exercise fails if http_proxy is not set, e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-zesty/zesty/amd64/l/lxc/20170320_194539_28897@/log.gz
Since the script uses 'set -e' the expression 'if [ -n "${http_proxy}"
]' causes the script to terminate when http_proxy isn't set.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1674679/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1713674 Title: Starting Xenial lxc without cap_sysadmin fails Status in lxc package in Ubuntu: Fix Released Bug description: Dear all, When trying to start an LXC container with Xenial on both host and container, if sys_admin capability is dropped (lxc.cap.drop = sys_admin in the config file), the container fails to start, because systemd fails to mount the cgroup filesystem in the container. The workaround is to manually mount the cgroup filesystem before starting the container (using the lxc.mount.entry in the config file), but, LXC performs the mount too early, before being in the container cgroup namespace, that means what's mounted matches host cgroup namespace, not container namespace. The bug was already reported upstream[1][2], but didn't make it to Ubuntu yet, AFAIK. A fix was merged in master[3], would it be possible to have it in Ubuntu Xenial? So far, we manually patch Ubuntu LXC packages with that patch and observed no régressions. Thanks! Cheers, P. Schweitzer [1]: https://github.com/lxc/lxc/pull/1597 [2]: https://github.com/lxc/lxc/pull/1606 [3]: https://github.com/lxc/lxc/commit/c1cecfdd050818865653d7941d7bae5d755246ae To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1713674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1586608 Title: Can not start nested trusty container inside trusty container Status in lxc package in Ubuntu: Won't Fix Bug description: On Xenial, can not start a nested Trusty container inside a Trusty container. (All containers are privileged, tests done on two different machines, one is a fresh Xenial install) Steps to reproduce: * Create a nested Trusty container (ie. Trusty container in a trusty container) on a Xenial machine * Observe the result: # lxc-start -d --name testt --logfile=/tmp/log lxc-start: lxc_start.c: main: 341 The container failed to start. lxc-start: lxc_start.c: main: 343 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 345 Additional information can be obtained by setting the --logfile and --logpriority options. # cat /tmp/log lxc-start 1464425901.410 ERRORlxc_cgfs - cgfs.c:cgfs_init:2246 - cgroupfs failed to detect cgroup metadata lxc-start 1464425901.411 ERRORlxc_start - start.c:lxc_spawn:884 - failed initializing cgroup support lxc-start 1464425901.467 ERRORlxc_start - start.c:__lxc_start:1121 - failed to spawn 'testt' lxc-start 1464425901.467 ERRORlxc_start_ui - lxc_start.c:main:341 - The container failed to start. lxc-start 1464425901.467 ERRORlxc_start_ui - lxc_start.c:main:343 - To get more details, run the container in foreground mode. lxc-start 1464425901.467 ERRORlxc_start_ui - lxc_start.c:main:345 - Additional information can be obtained by setting the --logfile and --logpriority options. Unsure if this is a Xenial or Trusty issue (tested on original 4.4.0-22-generic and 4.5.3 kernels) Works successfully (tested): * On Xenial, Xenial container inside Xenial container * On Xenial, Trusty container inside Xenial container * On Trusty, Trusty container inside Trusty container Does NOT work: * On Xenial, Trusty container inside Trusty container Setup details: * Create container: apt-get update --yes apt-get dist-upgrade --yes apt-get install lxc --yes lxc-create -n NAME -t ubuntu -- -r trusty -a amd64 --or-- lxc-create -n NAME -t ubuntu -- -r xenial -a amd64 And add in config: lxc.include = /usr/share/lxc/config/nesting.conf Also, for Xenial: lxc.aa_allow_incomplete = 1 Then start and attach to create the nested container. Additional information: * On the Trusty container on a Xenial machine: # cat /proc/cgroups #subsys_name hierarchy num_cgroups enabled cpuset9 12 1 cpu 2 164 1 cpuacct 2 164 1 blkio 7 164 1 memory5 702 1 devices 10 319 1 freezer 11 28 1 net_cls 8 12 1 perf_event3 12 1 net_prio 8 12 1 hugetlb 6 12 1 pids 4 305 1 # uname -a Linux testt 4.5.3 #1 SMP Mon May 9 08:18:24 CEST 2016 x86_64 x86_64 x86_64 GNU/Linux Also tested on a regular 4.4.0-22 kernel: # uname -a Linux xavier-test 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux # cat /proc/self/mountinfo 164 119 202:1 /var/lib/lxc/testt/rootfs / rw,noatime master:1 - ext4 /dev/xvda1 rw,nobarrier,errors=remount-ro,data=ordered 165 164 0:44 / /dev rw,relatime - tmpfs none rw,size=492k,mode=755 166 164 0:43 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw 167 168 0:43 /sys/net /proc/sys/net rw,nosuid,nodev,noexec,relatime - proc proc rw 168 166 0:43 /sys /proc/sys ro,nosuid,nodev,noexec,relatime - proc proc rw 169 166 0:43 /sysrq-trigger /proc/sysrq-trigger ro,nosuid,nodev,noexec,relatime - proc proc rw 170 164 0:45 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 171 170 0:45 / /sys rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 172 171 0:45 / /sys/devices/virtual/net rw,relatime - sysfs sysfs rw 173 172 0:45 /devices/virtual/net /sys/devices/virtual/net rw,nosuid,nodev,noexec,relatime - sysfs sysfs rw 174 171 0:37 / /sys/fs/fuse/connections rw,relatime master:28 - fusectl fusectl rw 175 171 0:7 / /sys/kernel/debug rw,relatime master:25 - debugfs debugfs rw 176 171 0:12 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime master:8 - securityfs securityfs rw 177 171 0:23 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime master:11 - pstore pstore rw 178 165 0:42 / /dev/mqueue rw,relatime - mqueue mqueue rw 179 165 0:43 / /dev/.lxc/proc rw,relatime - proc proc rw 180 165 0:45 / /dev/.lxc/sys rw,relatime - sysfs sys rw 181
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1511197 Title: PCI Device Access Through /proc/ Status in lxc package in Ubuntu: Fix Released Bug description: PCI Device Control Region Access From Within Containers #Summary: * From within a container, it is possible to access the control regions of devices attached to the host PCI bus by using the /proc/bus/pci/ interface. This is allowed because of the CAP_SYS_RAWIO capability which is by default enabled inside an LxC container. This proof of concept uses this vulnerability to speak to an AHCI device directly, and ask a SATA drive to identify itself (although it could trivially be used to create a denial-of-service of the drive instead). The usage of an AHCI drive is an arbitrary choice, a different approach may be to go after other targets on the PCI bus, such as the network controller. * This proof of concept is meant to demonstrate the ability to circumvent containerization by communicating with underlying hardware directly. It is likely this could be leveraged into full access to the underlying hard disk, however, this exploitation would be quite complicated, and is discussed in full later. #Reproduction: * The test environment for me was a vmware workstation system running Ubuntu. The primary disk was a SCSI disc, but I added a secondary 1GB SATA disk, with no special settings (write caching was enabled by default). You can talk to it if it's mounted or not. * I created a default LxC environment using the instructions at https://help.ubuntu.com/lts/serverguide/lxc.html. * As the root user in the LxC container, I used lspci -vv to get the information about the target AHCI device: 02:05.0 SATA controller: VMware Device 07e0 (prog-if 01 [AHCI 1.0]) Subsystem: VMware Device 07e0 Physical Slot: 37 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- ports_impl: 0x3fff - port 0 - command list base address: 0x0 FIS base address: 0x14c29000 interrupt status: 0x0 interrupt enable: 0x7840007f PORT_IRQ_D2H_REG_FIS PORT_IRQ_PIOS_FIS PORT_IRQ_DMAS_FIS PORT_IRQ_SDB_FIS PORT_IRQ_UNK_FIS PORT_IRQ_SG_DONE PORT_IRQ_CONNECT PORT_IRQ_PHYRDY PORT_IRQ_IF_ERR PORT_IRQ_HBUS_DATA_ERR PORT_IRQ_HBUS_ERR PORT_IRQ_TF_ERR command and status: 0x44016 PORT_CMD_SPIN_UP PORT_CMD_POWER_ON PORT_CMD_FIS_RX PORT_CMD_FIS_ON signature : 0x101 (SATA drive) tfd : 0x441 status : 0x123 errors : 0x0 active : 0x0 control : 0x320 --- interrupt status before: 0x0 start bit before: 0 interrupt status after: 0x2 PORT_IRQ_PIOS_FIS Waiting for command completion Seems to have completed... Got response data in DMA buffer: 0x7f5a27873000: 7a 42 ab 08 00 00 0f 00 00 00 00 00 3f 00 00 00 zB... ... 0x7f5a27873010: 00 00 00 00 30 30 30 30 30 30 30 30 30 30 30 30 0 000 0x7f5a27873020: 30 30 30 30 30 30 31 30 00 00 40 00 00 00 30 30 0010. .00 0x7f5a27873030: 30 30 30 30 31 30 4d 56 61 77 65 72 56 20 72 69 10MVa werV.ri 0x7f5a27873040: 75 74 6c 61 53 20 54 41 20 41 61 48 64 72 44 20 utlaS.TA. AaHdrD. 0x7f5a27873050: 69 72 65 76 20 20 20 20 20 20 20 20 20 20 ff 80 irev. ... 0x7f5a27873060: 00 00 00 0f 01 40 00 02 00 00 07 00 ab 08 0f 00 . ... 0x7f5a27873070: 3f 00 3b ff 1f 00 ff 01 00 00 20 00 00 00 07 00 . ... 0x7f5a27873080: 03 00 78 00 78 00 78 00 78 00 00 00 00 00 00 00 ..x.x.x.x ... 0x7f5a27873090: 00 00 00 00 00 00 1f 00 06 01 00 00 00 00 00 00 . ... 0x7f5a278730a0: 7e 00 18 00 08 40 08 74 00 41 08 40 80 34 00 41 ...t. A...4.A [SNIP] * The hexdump output shows the ATA IDENTIFY command response sent back from the controller. * There are some assumptions the code makes. It assumes the drive it is going to talk to is the first device it finds in the AHCI port list that is actually active. * Also it doesn't cleanly recover everything after getting the response, so the state of the mapped registers is wrong and the kernel won't be able to mount the device afterwards or anything. # Explanation of PoC While reading the attached code is instructive, here is an overview of the methodology used: * Map the control region of the AHCI device into memory through the /proc/bus/pci/ interface using open(), mmap(), and ioctl(). * Allocate
[Touch-packages] [Bug 1527374] Re: CVE-2015-8709
** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1527374 Title: CVE-2015-8709 Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Confirmed Status in linux-flo package in Ubuntu: Confirmed Status in linux-goldfish package in Ubuntu: Confirmed Status in linux-lts-quantal package in Ubuntu: Won't Fix Status in linux-lts-raring package in Ubuntu: Won't Fix Status in linux-lts-saucy package in Ubuntu: Won't Fix Status in linux-lts-utopic package in Ubuntu: Fix Released Status in linux-lts-vivid package in Ubuntu: Fix Released Status in linux-lts-wily package in Ubuntu: Fix Released Status in linux-lts-xenial package in Ubuntu: New Status in linux-mako package in Ubuntu: Confirmed Status in linux-manta package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: New Status in linux-ti-omap4 package in Ubuntu: Confirmed Status in linux source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Vivid: Fix Released Status in linux source package in Wily: Fix Released Status in linux source package in Xenial: Fix Released Bug description: ** DISPUTED ** kernel/ptrace.c in the Linux kernel through 4.4.1 mishandles uid and gid mappings, which allows local users to gain privileges by establishing a user namespace, waiting for a root process to enter that namespace with an unsafe uid or gid, and then using the ptrace system call. NOTE: the vendor states "there is no kernel bug here." Break-Fix: - local-2015-8709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1556110 Title: package lxc (not installed) failed to install/upgrade: 子程序 已安裝的 post- installation script 傳回了錯誤退出狀態 1 Status in lxc package in Ubuntu: Invalid Bug description: unable to remove ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lxc (not installed) ProcVersionSignature: Ubuntu 3.13.0-81.125-generic 3.13.11-ckt35 Uname: Linux 3.13.0-81-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: lxc-templates: Purge lxc: Configure Architecture: amd64 Date: Wed Mar 9 19:23:05 2016 DuplicateSignature: package:lxc:(not installed):子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1 ErrorMessage: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1 InstallationDate: Installed on 2014-12-29 (437 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: lxc Title: package lxc (not installed) failed to install/upgrade: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1556110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: Won't Fix Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1594751 Title: lxc-ls doesn't show nested containers when using an alternate lxc path Status in lxc package in Ubuntu: Incomplete Bug description: Ubuntu 16.04 PAckage : dpkg -l|grep lxc ii liblxc1 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (library) ii lxc 2.0.1-0ubuntu1~16.04.1 all Transitional package for lxc1 ii lxc-common 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (common tools) ii lxc-templates2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools ii lxcfs2.0.1-0ubuntu1~16.04.1 amd64 FUSE based filesystem for LXC ii python3-lxc 2.0.1-0ubuntu1~16.04.1 amd64 Linux Containers userspace tools (Python 3.x bindings) Same problem than https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1177412 If a container path is not the default one, lxc-ls can't give container information, even with -P path/container options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1594751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869035] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869035 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: New Bug description: i wanted to install wine 5.0 and there is errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Wed Mar 25 16:57:57 2020 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3.10) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3.10_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2017-09-28 (908 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1869035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1521151 Title: init: lxc-instance main process terminated with status 255 Status in lxc package in Ubuntu: Won't Fix Bug description: We have a trusty host which has 9 trusty guests running under LXC. On the most recent reboot, 3 of the LXC processes crashed: [ 10.912793] init: lxc-instance (nz-prod-bdbbackup-akl3) main process (3175) terminated with status 255 [ 11.031717] init: lxc-instance (au-prod-db-akl3) main process (2974) terminated with status 255 [ 11.079716] init: lxc-instance (au-test-backup-akl3) main process (3042) terminated with status 255 We were able to manually start them afterwards, but it's not clear why they crashed on boot. Each of those containers has identical software configurations to at least one of the 6 containers that didn't crash on boot, so it appears to be random. We're running the 3.13.0-68-generic kernel and LXC 1.0.7-0ubuntu0.10. All other packages are current. Here is a sample config: # Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu # Parameters passed to the template: -r trusty --user --auth-key /home//.ssh/authorized_keys # For additional config options, please look at lxc.container.conf(5) # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf # Container specific configuration lxc.rootfs = /var/lib/lxc/au-test-backup-akl3/rootfs lxc.mount = /var/lib/lxc/au-test-backup-akl3/fstab lxc.utsname = au-test-backup-akl3 lxc.arch = amd64 # Network configuration lxc.network.type = veth lxc.network.flags = up lxc.network.link = br0 lxc.network.hwaddr = 00:16:3e:9e:7c:41 lxc.network.type = veth lxc.network.flags = up lxc.network.link = br1 lxc.network.hwaddr = 00:16:3f:18:88:d9 lxc.start.auto = 1 And fstab: /var/backups/au-test-backup-akl3 var/backups bind defaults,bind 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1521151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1472929 Title: undefined symbol: cgmanager_get_pid_cgroup_abs_sync Status in lxc package in Ubuntu: Invalid Bug description: I have lxc installed on 14.04 , I am getting following error while running lxc-create command dtripathi@dtripath-x:~$ sudo lxc-create -t default -n dtripathi-lxc01 lxc-create: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblxc.so.1: undefined symbol: cgmanager_get_pid_cgroup_abs_sync dtripathi@dtripathi-x:~$ ldd /usr/bin/lxc-create linux-vdso.so.1 => (0x7ffd3a7e8000) liblxc.so.1 => /usr/lib/x86_64-linux-gnu/liblxc.so.1 (0x7fbc91aa) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbc91882000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbc914bb000) libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fbc912b6000) libapparmor.so.1 => /usr/lib/x86_64-linux-gnu/libapparmor.so.1 (0x7fbc910aa000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x7fbc90e86000) libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2 (0x7fbc90c6f000) libcgmanager.so.0 => /lib/x86_64-linux-gnu/libcgmanager.so.0 (0x7fbc90a55000) libnih.so.1 => /lib/x86_64-linux-gnu/libnih.so.1 (0x7fbc9083c000) libnih-dbus.so.1 => /lib/x86_64-linux-gnu/libnih-dbus.so.1 (0x7fbc90632000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7fbc903ed000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fbc901e9000) /lib64/ld-linux-x86-64.so.2 (0x7fbc91f2d000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fbc8ffab000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbc8fda6000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fbc8fb9e000) dtripathi@dtripathi-:~$ Please find the To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1472929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1441307 Title: lxc-clone makes new copies of each hardlinked file Status in lxc package in Ubuntu: Fix Released Bug description: I'm using lxc 1.0.7 from the stable PPA on precise. When I use lxc-clone to copy a container running MAAS, which uses hardlinks to manage images, each hardlinked file is created as a new file in the cloned rootfs, increasing my file system size by hundreds of GB's. rsync is not using -H - just rsync -a. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1441307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436722 Title: lxc domain setup instructions are incorrect Status in lxc package in Ubuntu: Triaged Bug description: Developers are required to manually hack their configuration to enable .lxc domain name resolution. This appears to be documented solely in /etc/default/lxc-net. This documentation is incorrect, as it tells developers to edit /etc/dnsmasq.conf and this file does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1359224 Title: Feature request: Add support for multiple bridges Status in lxc package in Ubuntu: Triaged Bug description: I want to allow multiple users to create unpriviledged containers on the same host. And I would like each user to be assigned a different bridge, so that each user's containers can be restricted to a sub-net. The `/etc/init/lxc-ent` script seems to be hard-coded for one bridge. If it could read a list of bridge names and create them automatically, it would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1359224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1445539 Title: Can't create vivid lxc on trusty Status in lxc package in Ubuntu: Won't Fix Bug description: When I create a vivid lxc in trusty like this: lxc-create -t ubuntu -n vivid-lxc -- -r vivid I get this error at the end: Hit http://archive.ubuntu.com vivid-updates/universe Translation-en │·· Reading package lists... Done │·· Reading package lists... Done │·· Building dependency tree... Done │·· Package lxcguest is not available, but is referred to by another package. │·· This may mean that the package is missing, has been obsoleted, or │·· is only available from another source │·· E: Package 'lxcguest' has no installation candidate │·· To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1445539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1532069 Title: Can't create a container with a loop backing store in 1.0.8 Status in lxc package in Ubuntu: Incomplete Bug description: Since version 1.0.8 of the lxc package in trusty it appears that it's no longer possible to create a container with a loop backing store. To reproduce the issue, install version 1.0.8-0ubuntu0.3 of the lxc, liblxc1 and python3-lxc packages on trusty and run the following: root@c4b2:/var/lib/lxc# /usr/bin/lxc-create -l DEBUG -n testcontainer --bdev loop -t ubuntu -- -r precise lxc_container: bdev.c: do_loop_create: 2036 Error creating filesystem type ext3 on /var/lib/lxc/testcontainer/rootdev lxc_container: lxccontainer.c: do_bdev_create: 819 Failed to create backing store type loop lxc_container: lxccontainer.c: lxcapi_create: 1299 Error creating backing store type loop for testcontainer lxc_container: lxc_create.c: main: 274 Error creating container testcontainer If I downgrade all the lxc packages to 1.0.7 on the same system it works fine. This issue is similar to what was reported in https://lists.linuxcontainers.org/pipermail/lxc- users/2015-September/010092.html but in that case the issue was occurring when running with backport versions 1.1.3, 1.1.2 but again, not with version 1.0.7. Please let me know if you require further information. Mike. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1532069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1537939 Title: apparmor profile for /var/lib/lxd denies mount operation on container creation Status in lxc package in Ubuntu: Fix Released Bug description: When I create a container using "lxc launch ubuntu", apparmor logs the following denial: Jan 25 17:05:58 x kernel: [32910.202500] audit: type=1400 audit(1453763158.495:185): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxd-louche- ettie_" name="/sys/" pid=7619 comm="mount" flags="rw, nosuid, nodev, noexec, remount" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apparmor 2.10-0ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 25 17:07:32 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-13 (73 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1537939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1544157 Title: lxc exec not working in xenial Status in lxc package in Ubuntu: Fix Released Bug description: My host is on the very latest Xenial as of yesterday Feb9,2016 My work flow has been... $ newgrp lxd $ lxc images:ubuntu/xenial/amd64 xen $ lxc start xen $ lxc exec xen -- /bin/bash at the moment, the image creation works, i can list my images - and it says they are running however, upon exec i'm not logged onto the shell - no output, even if i pass --verbose=true To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1544157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1533244 Title: lxc-net thinks it's already running after it failed Status in lxc package in Ubuntu: Incomplete Bug description: When lxc-net fails (because dnsmasq failed to bind on an interface), it claims to actually be running (the /var/run/lxc/network_up file is present) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.5-0ubuntu0.15.10.3 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 12 14:49:06 2016 InstallationDate: Installed on 2012-08-17 (1242 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-12-06 (37 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1533244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1537689
Title:
ubuntu template fro lxc messes up proxies
Status in lxc package in Ubuntu:
Won't Fix
Bug description:
In our corporate we have a cumbersome installation of proxies:
* (ProxyA) One proxy for the internet access (not capable of supporting apt
correctly)
* (ProxyB) One apt-cacher-ng for the apt package mirroring
So we have a configuration:
http_proxy=ProxyA
...
and in our apt-config we have ProxyB
Now running the default template for ubuntu messes these things
completely up by setting the ProxyB for all or vice versa, dependent
on the basic configuration. For me the function to choose the
container proxy looks very weird and complicated, for e.g. if an apt-
proxy is available he uses this for the normal http proxy too and vice
versa.
My question is, if the variables are set correctly, how can we achieve
the correct setting and I altered the template to have only this
function:
choose_container_proxy()
{
local rootfs=$1
local arch=$2
# Detecting apt-proxy
RES=`apt-config shell APT_PROXY Acquire::http::Proxy`
eval $RES
}
Ok, now the squid think was lost, but I am not sure why it is needed. As far
as I know the http_proxy environments can do the trick if set correctly. If
these things were not set correctly the normal system will also not run as
needed.
Maybe a better option would be to make this configurable by the
/etc/defaults/lxc file which will normally do the direct way and if it
is needed, the proxy search beahvior can be overwritten or changed
there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1537689/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1548497 Title: Cross-Container ARP Poisoning Status in lxc package in Ubuntu: Won't Fix Bug description: Description: An unprivileged LXC container can conduct an ARP spoofing attack against another unprivileged LXC container running on the same host. This allows man-in-the-middle attacks on another container's traffic. Recommendation: Due to the complex nature of this involving the Linux bridge interface, NCC is not aware of an easy fix. We suggest involving the kernel networking team to allow for ARP restrictions on virtual bridge interfaces. Using ebtables to block and control link layer traffic may also be an effective fix. Documentation should reflect the risks of not using any future protections or ebtables. Reproduction: This was found to work on an LXC deployment in AWS. It was then tested on a local Ubuntu VM. For the purposes of reproducibility, the following is an extremely explicit guide to reproducing the issue: # First, a Ubuntu Trusty 64 VM was setup using vagrant: vagrant init ubuntu/trusty64 vagrant up vagrant ssh # Now, inside the new Ubuntu VM: apt-get update apt-get install lxc # set up two unprivileged LXC containers (from https://help.ubuntu.com/lts/serverguide/lxc.html) mkdir -p ~/.config/lxc echo "lxc.id_map = u 0 10 65536" > ~/.config/lxc/default.conf echo "lxc.id_map = g 0 10 65536" >> ~/.config/lxc/default.conf echo "lxc.network.type = veth" >> ~/.config/lxc/default.conf echo "lxc.network.link = lxcbr0" >> ~/.config/lxc/default.conf echo "$USER veth lxcbr0 2" | sudo tee -a /etc/lxc/lxc-usernet lxc-create -t download -n a -- -d ubuntu -r trusty -a amd64 lxc-create -t download -n b -- -d ubuntu -r trusty -a amd64 # fix cgroup issues (from https://github.com/lxc/lxc/issues/181) for c in hugetlb cpuset cpu cpuacct memory devices freezer blkio perf_event; do sudo dbus-send --print-reply --address=unix:path=/sys/fs/cgroup/cgmanager/sock \ --type=method_call /org/linuxcontainers/cgmanager org.linuxcontainers.cgmanager0_0.Create \ string:$c string:$USER sudo dbus-send --print-reply --address=unix:path=/sys/fs/cgroup/cgmanager/sock \ --type=method_call /org/linuxcontainers/cgmanager org.linuxcontainers.cgmanager0_0.Chown \ string:$c string:$USER int32:$(id -u) int32:$(id -g) dbus-send --print-reply --address=unix:path=/sys/fs/cgroup/cgmanager/sock \ --type=method_call /org/linuxcontainers/cgmanager org.linuxcontainers.cgmanager0_0.MovePid \ string:$c string:$USER int32:$$ done #start the containers lxc-start -n a -d lxc-start -n b -d # open two new terminal windows # in one: attach to container A lxc-attach -n a # in another: attach to container B lxc-attach -n b # from now on, all commands will have the full command prompt to make it clear where they are being run # look at the ARP tables on the host: root@vagrant-ubuntu-trusty-64:~# arp -a ? (10.0.2.2) at 52:54:00:12:35:02 [ether] on eth0 ? (10.0.3.159) at e2:33:5d:33:cf:07 [ether] on lxcbr0 ? (10.0.3.246) at e6:ad:42:7a:f1:54 [ether] on lxcbr0 ? (10.0.2.3) at 52:54:00:12:35:03 [ether] on eth0 # in this case, 10.0.3.159 is container B's eth0, and 10.0.3.246 is container A's eth0 # since the two containers are on the same subnet, it may appear that they can sniff each other's traffic # a quick demonstration that you cannot normally sniff traffic on the wire just by virtue of being on the same subnet: # in container A root@a:/# tcpdump -i any -vv -n dst host 10.0.3.159 # in container B root@b:/# nc -lv # on the host (type something in the nc session, and note no traffic is output in container A) vagrant@vagrant-ubuntu-trusty-64:~$ nc 10.0.3.83 # now, we will demonstrate the ability to sniff traffic with ARP spoofing # in container A: # install dsniff apt-get update apt-get install dsniff # ARP spoof the host: arpspoof -t 10.0.3.1 10.0.3.159 &>/dev/null & # look at the ARP tables on the host and note that both 10.0.3.159 and 10.0.3.246 both now point at the MAC address for container A: root@vagrant-ubuntu-trusty-64:~# arp -a ? (10.0.2.2) at 52:54:00:12:35:02 [ether] on eth0 ? (10.0.3.159) at e6:ad:42:7a:f1:54 [ether] on lxcbr0 ? (10.0.3.246) at e6:ad:42:7a:f1:54 [ether] on lxcbr0 ? (10.0.2.3) at 52:54:00:12:35:03 [ether] on eth0 # note that container B can no longer access the internet
[Touch-packages] [Bug 1869012] Re: [nvidia] Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1868396 *** https://bugs.launchpad.net/bugs/1868396 ** Summary changed: - Xorg freeze + [nvidia] Xorg crashed with SIGABRT ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** This bug has been marked a duplicate of bug 1868396 crashes or freezes with nividia/xorg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869012 Title: [nvidia] Xorg crashed with SIGABRT Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Well, that is maybe a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868396 More crash info in : https://errors.ubuntu.com/oops/4dd7bfc4-6ea1 -11ea-98a4-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:04:06 2020 DistUpgraded: 2019-11-04 11:06:46,434 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-42-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2019-04-26 (333 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-04 (142 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548731] Re: autostart on boot not working
This is fixed in modern versions of LXC using systemd. ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1548731 Title: autostart on boot not working Status in lxc package in Ubuntu: Fix Released Bug description: Description: Ubuntu 14.04.4 LTS Release: 14.04 lxc: Installed: 1.0.8-0ubuntu0.3 Candidate: 1.0.8-0ubuntu0.3 Upstart service /etc/init/lxc.conf should start all LXC containers having set "lxc.start.auto = 1" if /etc/default/lxc got LXC_AUTO="true". This does not work on a "reboot"/"shutdown -r now" but it does work after a reboot using "restart lxc". It fails because of missing network devices (early boot up stage): lxc-start: conf.c: instantiate_veth: 3105 failed to attach 'vethMCUSEO' to the bridge 'lxcfr258': No such device lxc-start: conf.c: lxc_create_network: 3388 failed to create netdev lxc-start: start.c: lxc_spawn: 856 failed to create the network lxc-start: start.c: __lxc_start: 1121 failed to spawn 'xx' lxc-start: lxc_start.c: main: 341 The container failed to start. lxc-start: lxc_start.c: main: 345 Additional information can be obtained by setting the --logfile and --logpriority options. We do use a special veth setup but the lxc upstart service should still cover this case. --- /etc/init/lxc.conf2015-11-18 20:08:53.0 +0100 +++ /tmp/lxc.conf 2016-02-23 11:30:08.704830042 +0100 @@ -1,7 +1,7 @@ description "lxc" author "Serge Hallyn " -start on runlevel [2345] +start on started networking stop on starting rc RUNLEVEL=[016] env LXC_AUTO="false" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1548731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1542438 Title: Python LXC api needs to be much better at error reporting Status in lxc package in Ubuntu: Won't Fix Bug description: I use the Python API extensively on the lp:libertine project. However, when there is an error somewhere in the LXC layer, the only thing that is returned is False which is not very useful when trying to figure out what has gone wrong. For example, I try to use the Container.create() method and it is failing However, when I try using the lxc-create CLI tool using the same exact parameters, it works. Since the Python API does not have an error output, I'm having a very difficult time figuring out why the Python create is failing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1542438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1530617] Re: FUSE in wily image with upstart installed causes chaos
** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid ** Changed in: upstart (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1530617 Title: FUSE in wily image with upstart installed causes chaos Status in linux package in Ubuntu: Invalid Status in lxc package in Ubuntu: Invalid Status in upstart package in Ubuntu: Won't Fix Bug description: Host: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu 15.10" lxc version: 1.1.4-0ubuntu1 In a LXC container running Ubuntu 15.10, install upstart-sysv to replace systemd. Using FUSE then causes almost all processes in the container to be killed. The following steps reproduce the problem using sshfs: # create a wily container and attach to it sudo lxc-create -t download -n wily -- -d ubuntu -r wily -a amd64 sudo lxc-start -n wily sudo lxc-attach -n wily # inside the container, install upstart-sysv and reboot apt-get update && apt-get -y install upstart-sysv reboot # on the host, reattach to the container sudo lxc-attach -n wily # back in the container, install ssh and sshfs apt-get -y install openssh-server sshfs # create an ssh key pair in /root/.ssh ssh-keygen # set up passwordless ssh mkdir ~ubuntu/.ssh cat /root/.ssh/id_rsa.pub >> ~ubuntu/.ssh/authorized_keys eval $(ssh-agent) ssh-add /root/.ssh/id_rsa # take a note of the running processes and their PIDs ps axjf # run sshfs mkdir /fuse sshfs ubuntu@localhost:/ /fuse # we are kicked out of the container # run ps again in the container sudo lxc-attach -n wily -- ps axjf # a whole bunch of processes are now gone. the getty processes now have new PIDs, indicating they have been restarted. Other debugging performed: - On a 14.10 host with lxc version 1.1.0~alpha2-0ubuntu3.3, the problem does not occur. FUSE works fine. - On the same 14.10 host with lxc upgraded to 1.1.5-0ubuntu3~ubuntu14.04.1, the problem occurs. - On a 15.10 host, when running a wily container without upstart, the problem does not occur. - On a 15.10 host, when running a trusty container, the problem does not occur. - The problem can't be reproduced outside a container (15.10 host, install upstart-sysv, then use FUSE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184936] Re: lxc-clone freezes if copied container is running [12.04 kernel 3.8]
** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1184936 Title: lxc-clone freezes if copied container is running [12.04 kernel 3.8] Status in lxc package in Ubuntu: Fix Released Bug description: Cloning running container freezes (stops responding), stopping that container in second shell unfreezes clone process and successfully clones container. # uname -a Linux air 3.8.0-22-generic #33~precise1-Ubuntu SMP Fri May 17 00:58:43 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux # apt-cache policy lxc lxc: Installed: 0.8.0~rc1-4ubuntu38~ubuntu12.04.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1184936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1519228 Title: Drop obsolete dh_installinit --upstart-only option Status in avahi package in Ubuntu: Fix Released Status in console-setup package in Ubuntu: Fix Released Status in cups package in Ubuntu: Fix Released Status in dcbd package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in hostname package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in nfs-utils package in Ubuntu: Fix Released Status in nis package in Ubuntu: Fix Released Status in rfkill package in Ubuntu: Fix Released Status in xdiagnose package in Ubuntu: Fix Released Bug description: dh_installinit's --upstart-only option has been a deprecated no-op for a long time. Drop the remaining usage of it in packages so that we can get rid of this delta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1519228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475751] Re: need phablet support for mods to /etc/lxc/lxc-usernet (vivid+stable ppa overaly)
** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix ** Changed in: canonical-devices-system-image Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1475751 Title: need phablet support for mods to /etc/lxc/lxc-usernet (vivid+stable ppa overaly) Status in Canonical System Image: Invalid Status in lxc package in Ubuntu: Won't Fix Bug description: we have a need for phablet to use a network inside a container, currently the /etc/lxc/lxc-usernet file is readonly would need to be modified to contain something like phablet veth lxcbr0 10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1475751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452601] Re: vivid container's networking.service fails on boot with signal=PIPE
** Changed in: lxc (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452601 Title: vivid container's networking.service fails on boot with signal=PIPE Status in lxc package in Ubuntu: Won't Fix Bug description: When starting a Vivid container, it fails to get an IP address. It believes networking.service was successful, but actually it dies with SIGPIPE. Restarting networking.service gets an IP, as expected. Starting networking used to work with pre-vivid containers. I'm reasonably sure this fails 100% of the time. Limited user container, very standard setup (no unnecessary config; cgmanager and lxcfs installed), btrfs filesystem but not btrfs-backed (as it's limited user), ... root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (exited) since Thu 2015-05-07 07:54:48 UTC; 9s ago Docs: man:systemd-sysv-generator(8) Process: 459 ExecStart=/etc/init.d/networking start (code=killed, signal=PIPE) root@vivid:/# systemctl restart networking.service root@vivid:/# systemctl status networking.service ● networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf /lib/systemd/system/networking.service.d └─systemd.conf Active: active (running) since Thu 2015-05-07 07:56:38 UTC; 2s ago Docs: man:systemd-sysv-generator(8) Process: 992 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS) Process: 1033 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) CGroup: /user.slice/user-1000.slice/session-c2.scope/lxc/vivid/system.slice/networking.service ├─1096 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 ├─1106 /bin/sh /etc/network/if-up.d/ntpdate ├─1109 lockfile-touch /var/lock/ntpdate-ifup ├─1125 /bin/sh /etc/network/if-up.d/ntpdate ├─1128 lockfile-create /var/lock/ntpdate-ifup └─1146 /usr/sbin/ntpdate -s ntp.ubuntu.com root@vivid:/# ip a ... 22: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 ... inet 10.0.3.102/24 brd 10.0.3.255 scope global eth0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 7 08:53:02 2015 SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510108] Re: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24
** No longer affects: lxc (Ubuntu Wily) ** No longer affects: lxc (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1510108 Title: pre-installed lxc in cloud-image means loss of access to 10.0.X.0/24 Status in lxc package in Ubuntu: Triaged Bug description: Bug 1509414 describes fallout of inclusion of lxc in cloud images. The initial inclusion caused 2 issues: a.) containers created by 'lxc -t ubuntu-cloud' and 'lxd import-images ubuntu wily' had completely broken networking b.) all cloud images would have lost access to 10.0.3.0/24 networks. The fix that went in fixes 'a' above. By default, containers created for lxd and lxc will now work as expected. This bug is opened to address the much less severe 'b'. Now, on first boot lxc-net selects a network in the 10.0.X.0/24 to give to the lxcbr0 bridge. It selects the network by simply looking for the first available N where there . That code can be seen prior to fix in debian/lxc.preinst [1] and after fix in config/init/common /lxc-net.in [2]. Generally speaking it looks for local ip addresses on the targeted network. That code is fairly simplistic. There are definitely cases where it can pick a network that would be used by this system. The result is that traffic destined for that network will be sent to the lxcbr0 rather than out of the system to wherever it should go. The suggested fix would be to make that code run on 'lxc' or 'lxd' usage rather than on instance boot. By doing so, we reduce the set of users possibly affected from all cloud-image users to all users of lxc or lxd. Note, all users of lxd and lxc have been affected by this bug since at least 14.04. -- [1] https://github.com/lxc/lxc-pkg-ubuntu/blob/dpm-wily/debian/lxc.preinst#L55 [2] https://github.com/lxc/lxc-pkg-ubuntu/blob/dpm-wily/config/init/common/lxc-net.in Related bugs: * bug 1509414: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1510108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389864] Re: /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system
** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1389864 Title: /etc/dnsmasq.d-available/lxc has no effect on a NetworkManager system Status in lxc package in Ubuntu: Triaged Bug description: The lxc package installs dnsmasq configuration as /etc/dnsmasq.d-available/lxc, and a symlink to it is created at /etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq instance on systems running NetworkManager, because NetworkManager starts a dnsmasq instance that looks in /etc/NetworkManager/dnsmasq.d instead. This means that when someone adds server=/lxc/10.0.3.1 to lxc's dnsmasq config file, it doesn't work. I imagine it also leads to other configurations not working as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1389864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319525] Re: juju-local LXC containers hang due to AppArmor denial of rpc_pipefs mount with local charms
Been incomplete for years, closing. ** Changed in: lxc (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1319525 Title: juju-local LXC containers hang due to AppArmor denial of rpc_pipefs mount with local charms Status in juju-core: Invalid Status in lxc package in Ubuntu: Invalid Bug description: Ran into an issue with the local provider today that seems to be 'newish' behavior. steps to reproduce: juju bootstrap juju deploy cs:trusty/ubuntu juju deploy --repository=../ local:trusty/wordpress juju deploy cs:trusty/mysql Important to note - the race here, if mysql and ubuntu register the containers before the wordpress unit attempts to come online, things deploy as expected without wordpress coming online. The specifics of the wordpress unit preventing from starting were obtained with dmesg: [13804.451667] type=1400 audit(1400090535.864:127): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc- container-default" name="/run/rpc_pipefs/" pid=13800 comm="mount" fstype="rpc_pipefs" srcname="rpc_pipefs" flags="rw" Adding : mount fstype=rpc_pipefs, to /etc/apparmor.d/abstractions/lxc/container-base appears to have alleviated the behavior. Additional details: +++-===-==-==- ii juju-local 1.19.2-0ubuntu alldependency package for the Juju local provid ii juju1.19.2-0ubuntu allnext generation service orchestration system this is on 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1319525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396536] Re: lxc_start - Exec format error - failed to exec /sbin/init
We've not seen any other issue like this in the past 5 years, users usually know to pick something that they can actually run or know that they'll need to setup emulation. The error reported as weird as it is, is the expected behavior from the kernel when asked to run a foreign architecture binary, so no obvious bug to fix here nor really a way for LXC to distinguish that case from an actual permission issue. ** Changed in: lxc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1396536 Title: lxc_start - Exec format error - failed to exec /sbin/init Status in lxc package in Ubuntu: Invalid Bug description: I have an up to date Ubuntu 14.04. I followed the guide at https://help.ubuntu.com/lts/serverguide/lxc.html sudo apt-get install lxc && sudo lxc-create --template download --name u1 - Choose ubuntu-vivid-armhf, then: sudo lxc-start --name u1 --daemon lxc-start 1416996721.249 INFO lxc_apparmor - changed apparmor profile to lxc-container-default lxc-start 1416996721.249 NOTICE lxc_start - exec'ing '/sbin/init' lxc-start 1416996721.253 ERRORlxc_start - Exec format error - failed to exec /sbin/init lxc- $ sudo lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART u1STOPPED - - NO $ sudo lxc-checkconfig Kernel configuration not found at /proc/config.gz; searching... Kernel configuration found at /boot/config-3.13.0-24-generic --- Namespaces --- Namespaces: enabled Utsname namespace: enabled Ipc namespace: enabled Pid namespace: enabled User namespace: enabled Network namespace: enabled Multiple /dev/pts instances: enabled --- Control groups --- Cgroup: enabled Cgroup clone_children flag: enabled Cgroup device: enabled Cgroup sched: enabled Cgroup cpu account: enabled Cgroup memory controller: enabled Cgroup cpuset: enabled --- Misc --- Veth pair device: enabled Macvlan: enabled Vlan: enabled File capabilities: enabled Note : Before booting a new kernel, you can check its configuration usage : CONFIG=/path/to/config /usr/bin/lxc-checkconfig Except apt-get update and apt-get upgrade I didn't install any other packages (okay, I installed vim and git). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1396536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450960] Re: dev file system is mounted without nosuid
Marking as triaged/wishlist for LXC, I can't think of a good reason not to mount with nosuid so such a patch would still be welcome. ** Changed in: lxc (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1450960 Title: dev file system is mounted without nosuid Status in initramfs-tools package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Bug description: I just found that the /dev filesystem of most Ubuntu system is mounted without noexec, nosuid etc options. If you do everything to harden your system, and you are using squashfs as root file system (which is read-only), such auto-mounted devices can be a serious leak. This volume usually is quite small and for most folders only root has write access, so I don't know how much this bug is security relevant, but I think there is no reason to not change the mount options for /dev. And especially for LXC containers, I don't even know a workaround to fix it. STEPS TO REPRODUCE: me:~# cat >/dev/call-me.sh <<.e > #!/bin/sh > echo "I'm executable" > .e me:~# chmod +x /dev/call-me.sh me:~# /dev/call-me.sh I'm executable EXPECTED BEHAVIOUR me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied WORKAROUND me:~# mount -oremount,noexec,nosuid /dev me:~# /dev/call-me.sh -bash: /dev/call-me.sh: Permission denied Unfortunately, this workaround doesn't work in LXC containers (where the same problem occurs) because of missing capabilities. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: XFCE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied CustomUdevRuleFiles: 51-android.rules 60-vboxdrv.rules Date: Sat May 2 01:48:26 2015 MachineType: Gigabyte Technology Co., Ltd. H97-HD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=/dev/mapper/vg_ssd-lv_system_trusty1404 ro SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-18 (378 days ago) dmi.bios.date: 06/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/26/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1450960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1204662] Re: Language pack installation should be optional in ubuntu templates
We've moved away from those template scripts and are instead mostly relying on pre-made images. If building your own image through distrobuilder, you can add any additional packages you want at image building time. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1204662 Title: Language pack installation should be optional in ubuntu templates Status in lxc package in Ubuntu: Won't Fix Bug description: In lines 182 to 184, there should be a config option that toggles the installation of additional language packs. I may have several languages installed on my desktop, but I certainly do not want them on my test containers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1204662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1182458] Re: ubuntu-cloud template: use simplestreams to add integrity verification
The current donwload template model to download those images does do both https and gpg validation. ** Changed in: lxc (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1182458 Title: ubuntu-cloud template: use simplestreams to add integrity verification Status in lxc package in Ubuntu: Fix Released Bug description: Currently we wget the ubuntu-cloud template without any integrity verification. We then proceed to execute binaries like /bin/passwd while still in the ubuntu-cloud template (in a chroot, but without any effective containment). We should be verifying that the image we download has not been tampered with. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1182458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1867944] Re: Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins)
Thanks. Fix Released... somewhere. ** Package changed: pulseaudio (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1867944 Title: Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins) Status in Ubuntu: Fix Released Bug description: After upgrading Ubuuntu 18.04 LTS to 20.04 , when I watching Netflix(by Firefox) videos with my bluetooth speaker (Lasonic i931BT), I found that almost every 49mins ,the video suddenly slow down and then sound stop transmitting to my speaker. It shouldn't happen. I check the pulseaudio mixer's output device. My speaker dissappeared. Only "Dummy Output " showed. (As the screenshot ) Everytime, I need go to bluetooth manager to disconnect the speaker, and wait it automatically connects again. Sometimes it works, but sometimes does not. I need to reboot to fix it (Power off the speak won't help ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24 Uname: Linux 5.4.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 18 23:13:06 2020 InstallationDate: Installed on 2020-03-10 (8 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200130) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TCOP dmi.board.asset.tag: Tag 12345 dmi.board.name: ZX Series dmi.board.vendor: COPELION INTERNATIONAL INC. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: COPELION INTERNATIONAL INC. dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TCOP:bd10/14/2019:svnCOPELIONINTERNATIONALINC.:pnZXSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALINC.:rnZXSeries:rvrNotApplicable:cvnCOPELIONINTERNATIONALINC.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: ZX Series dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1867944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1266808] Re: No mechanism to wait until a started container is ready and has finished booting
After years of running LXC and LXD, this is a somewhat recurring topic which has no good answers, all distros do it differently and the definition of ready differs even user to user. So from LXC's point of view, it's best to stay away from this and instead have users actually check for what they care, be it a web service being ready, cloud-init indicating it's done running or whatever else and just use LXC's tools and API to run those checks. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1266808 Title: No mechanism to wait until a started container is ready and has finished booting Status in lxc package in Ubuntu: Won't Fix Bug description: If I script a container start, I also want to script a wait until the container has finished booting. Otherwise I start using the container, write to /tmp, and then /tmp gets cleaned. I'm sure there are more race conditions, too. It would be nice if lxc-wait could be extended to support some mechanism to detect this, or if not lxc-wait then some other generic mechanism that templates could then support. cloud-init writes a boot-finished flag which could be used on systems/templates that use cloud-init. Also see cloud-init bug 1258113. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1266808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1868474] Re: Lenovo ThinkPad P73 touchpad does not work *after* installation
This looks relevant: [ 6.732] (II) event6 - ETPS/2 Elantech Touchpad: device is a touchpad [ 6.732] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1) [ 6.732] (II) No input driver specified, ignoring this device. [ 10652.396] (II) config/udev: Adding input device Telink Wireless Receiver Mouse (/dev/input/mouse2) [ 10652.396] (II) No input driver specified, ignoring this device. ** Summary changed: - 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 + Lenovo ThinkPad P73 touchpad does not work *after* installation ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868474 Title: Lenovo ThinkPad P73 touchpad does not work *after* installation Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1289482] Re: "iscsiadm discovery" succeeds but "iscsiadm login" fails inside ubuntu container.
I'm pretty sure we've completely disabled iscsid inside containers at this point due to its tight link to un-namespaced kernel features. Some specific server use cases should be possible, but anything client related is unlikely to succeed without some major kernel work. ** Changed in: lxc (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1289482 Title: "iscsiadm discovery" succeeds but "iscsiadm login" fails inside ubuntu container. Status in lxc package in Ubuntu: Invalid Bug description: Here is output of commands - root@hytrust:~# iscsiadm -m discovery -t st -p 192.168.100.81 192.168.100.81:3260,1 iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server root@hytrust:~# ps -ef | grep iscsi root 398 1 0 13:58 ? 00:00:00 /usr/sbin/iscsid root 1305 1 0 14:06 ? 00:00:00 /usr/sbin/iscsid root 10744 1 0 16:15 ? 00:00:00 /usr/sbin/iscsid root 12899 10720 0 16:43 pts/1 00:00:00 grep --color=auto iscsi Now login fails - root@hytrust:~# iscsiadm -m node --targetname "iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server" --portal "192.168.100.81:3260" --login Logging in to iface: default, target: iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server, portal: 192.168.100.81,3260 iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: iqn.2014-03.in.co.coriolis.lan.hysrc:xbmc-server, portal: 192.168.100.81,3260]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals Same thing work if I do it from a Virtual Machine. I followed tutorial @ this link : http://www.heath-bar.com/blog/?p=184 It works perfect for virtual machines. We need this working as we are trying replace VMs with containers due to hardware limitation for scalability testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1289482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1043004] Re: --bindhome option should be on lxc-create, not on lxc-ubuntu
With current LXC, those templates aren't really a thing anymore and most of our users use unprivileged containers which require quite a bit more involved configuration to pass a host directory than just injecting a mount entry. If this is a useful pattern for a user, writing a dedicated ".conf" file for the system and passing that to `lxc-create` seems more appropriate. ** Changed in: lxc (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1043004 Title: --bindhome option should be on lxc-create, not on lxc-ubuntu Status in lxc package in Ubuntu: Won't Fix Bug description: The ubuntu template has a handy --bindhome option, but that's not very useful if you need to support multiple guest OS's. That option should be hoisted out of the template and into lxc-create itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1043004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869115] [NEW] python sys.path different per user account - ImportError no module named (Focal)
Public bug reported: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: path python sys ** Summary changed: - python sys.path different per user account - no module named + python sys.path different per user account - ImportError no module named ** Summary changed: - python sys.path different per user account - ImportError no module named + python sys.path different per user account - ImportError no module named (Focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869115 Title: python sys.path different per user account - ImportError no module named (Focal) Status in python2.7 package in Ubuntu: New Bug description: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869117] [NEW] python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
Public bug reported: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python2.7 package in Ubuntu: New Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869107] Re: Error when installing scanner deb on 20.04
Without looking at the deb file, this is likely a regression of 2.0 which was fixed in the recently released 2.0.1 in Debian. Pretty sure that will eventually flow into Ubuntu as well. See the commit in question for details if you are interested: https://salsa.debian.org /apt-team/apt/-/commit/bf46e09f0e4b52b3c71ac20bb11e7511fc16179f That the scanner doesn't seem to work for you is orthogonal to this issue. You might want to contact a support channel of Ubuntu about this with more details – bugreports tend not be a good place for getting hardware to behave with drivers in third-party packages. Thanks for reporting your issue none the less! ** Changed in: apt (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: Fix Committed Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')
I've attached the /var/log/syslog file which should be helpful to find out what went wrong ** Attachment added: "syslog - internet on, updates on, non-free drivers on - mod.txt" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1557739/+attachment/5341700/+files/syslog%20-%20internet%20on%2C%20updates%20on%2C%20non-free%20drivers%20on%20-%20mod.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1557739 Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') Status in apport package in Ubuntu: Confirmed Bug description: While running through the install, ubiquity crashed, then apport crashed so couldn't file a bug on ubiquity. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 -0400:2016-03-15 16:19:15.974973678 -0400:/var/crash/_usr_bin_apport-bug.999.crash Date: Tue Mar 15 16:19:15 2016 ExecutablePath: /usr/bin/apport-bug InterpreterPath: /usr/bin/python3.5 LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/apport-bug', 'ubiquity'] SourcePackage: apport Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1557739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869107] Re: Error when installing scanner deb on 20.04
Okay, well I was wrong. dpkg or gdebi will successfully install the .deb, but the scanner doesn't actually work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: New Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869107] [NEW] Error when installing scanner deb on 20.04
Public bug reported: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: New Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795651] Re: ICU data package is grossly outdated
@anrdaemon not sure what you mean. ICU itself doesn't cut a release every time there's a timezone update. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Status in icu package in Debian: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864869] Re: ICU returns unexpected length for string
I added a comment to the PHP bug, I think it is working as designed. Please track ICU bugs at https://unicode-org.atlassian.net (project ICU) thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1864869 Title: ICU returns unexpected length for string Status in icu package in Ubuntu: New Status in php7.4 package in Ubuntu: Invalid Bug description: Calculating the grapheme string length for the word 'नमस्ते' returns 3 instead of 4. This version returns unexpected result of 3: ICU version 65.1 ICU Data version 65.1 ICU TZData version2019c ICU Unicode version 12.1 This version returns the expected result of 4: ICU version => 63.1 ICU Data version => 63.1 ICU TZData version => 2018e ICU Unicode version => 11.0 PHP says this is an upstream issue: https://bugs.php.net/bug.php?id=79308 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1864869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')
This was the terminal output at the time of the crash. https://imgur.com/lgTRVKU.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1557739 Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') Status in apport package in Ubuntu: Confirmed Bug description: While running through the install, ubiquity crashed, then apport crashed so couldn't file a bug on ubiquity. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 -0400:2016-03-15 16:19:15.974973678 -0400:/var/crash/_usr_bin_apport-bug.999.crash Date: Tue Mar 15 16:19:15 2016 ExecutablePath: /usr/bin/apport-bug InterpreterPath: /usr/bin/python3.5 LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/apport-bug', 'ubiquity'] SourcePackage: apport Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1557739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1864869] Re: ICU returns unexpected length for string
Per the PHP bug, this appears not to be in php itself but rather higher up the stack. Reassigning to ICU for now. ** Also affects: icu (Ubuntu) Importance: Undecided Status: New ** Changed in: php7.4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1864869 Title: ICU returns unexpected length for string Status in icu package in Ubuntu: New Status in php7.4 package in Ubuntu: Invalid Bug description: Calculating the grapheme string length for the word 'नमस्ते' returns 3 instead of 4. This version returns unexpected result of 3: ICU version 65.1 ICU Data version 65.1 ICU TZData version2019c ICU Unicode version 12.1 This version returns the expected result of 4: ICU version => 63.1 ICU Data version => 63.1 ICU TZData version => 2018e ICU Unicode version => 11.0 PHP says this is an upstream issue: https://bugs.php.net/bug.php?id=79308 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1864869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557739] Re: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device')
As reported in #1868630, this crash happens to me when selecting 'Install Xubuntu Core' from the grub screen and doesnt happen when i let the installer start up normally without interaction. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1557739 Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') Status in apport package in Ubuntu: Confirmed Bug description: While running through the install, ubiquity crashed, then apport crashed so couldn't file a bug on ubiquity. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.367 CrashReports: 640:999:999:18776:2016-03-15 16:19:14.974973678 -0400:2016-03-15 16:19:15.974973678 -0400:/var/crash/_usr_bin_apport-bug.999.crash Date: Tue Mar 15 16:19:15 2016 ExecutablePath: /usr/bin/apport-bug InterpreterPath: /usr/bin/python3.5 LiveMediaBuild: Xubuntu Core 16.04 - amd64 - 20160314 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli ubiquity ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/apport-bug', 'ubiquity'] SourcePackage: apport Title: apport-bug crashed with termios.error in raw_input_char(): (25, 'Inappropriate ioctl for device') UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1557739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869078] [NEW] dhclient then ath10k firmware crashes
Public bug reported:
I had to restart so not sure if automatically generated debug-info is
relevant.
In my journalctl I get this error:
Mar 25 21:17:10 dhclient[29542]: For info, please visit
https://www.isc.org/software/dhcp/
Mar 25 21:17:10 dhclient[29542]:
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45:
numeric minute expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 45:
semicolon expected.
Mar 25 21:17:10 dhclient[29542]: rebind 3 2020/03/25 18:lease {
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 79:
expecting numeric value.
Mar 25 21:17:10 dhclient[29542]: option routers 192.168.0lease
Mar 25 21:17:10 dhclient[29542]: ^
Mar 25 21:17:10 dhclient[29542]: /var/lib/dhcp/dhclient.leases line 142:
unterminated lease declaration.
...
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: firmware crashed! (guid
9bfed658-d8c1-48ad-9172-538c9219d4df)
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: qca6174 hw3.2 target
0x0503 chip_id 0x00340aff sub 1a56:1535
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: kconfig debug 0 debugfs 1
tracing 1 dfs 0 testmode 0
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: firmware ver
WLAN.RM.4.4.1-00140-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32
29eb8ca1
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A
crc32 4ac0889b
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: htt-ver 3.60 wmi-op 4 htt-op
3 cal otp max-sta 32 raw 0 hwcrypto 1
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: failed to get memcpy hi
address for firmware address 4: -16
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: failed to read firmware dump
area: -16
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: Copy Engine register dump:
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [00]: 0x00034400 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [01]: 0x00034800 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [02]: 0x00034c00 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [03]: 0x00035000 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [04]: 0x00035400 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [05]: 0x00035800 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [06]: 0x00035c00 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:10 kernel: ath10k_pci :3a:00.0: [07]: 0x00036000 4294967295
4294967295 4294967295 4294967295
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to receive control
response completion, polling..
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
read32 at 0x0003: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00034430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00034830: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x0001 at 0x00035430: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
read32 at 0x00035444: -110
Mar 25 21:17:11 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00035430: -110
Mar 25 21:17:12 kernel: ath10k_pci :3a:00.0: failed to wake target for
write32 of 0x001e at 0x00034830: -110
Mar 25 21:17:13 kernel: ath10k_pci :3a:00.0: ctl_resp never came in (-110)
Mar 25 21:17:13 kernel: ath10k_pci :3a:00.0: failed to connect to HTC: -110
Full debug log attached.
My system froze. I was watching a move and the video stopped, audio
skipped. Hence why there are alsa complaints in the debug.
The ath10k firmware crashed and I couldn't reload.
Ubuntu 18.04.4 LTS
Linux albert-XPS-13-9360 5.5.0-050500-generic #202001262030 SMP Mon Jan
27 01:33:36 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
*-network
description: Wireless interface
product: QCA6174 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@:3a:00.0
logical name: wlp58s0
version: 32
serial: 9c:b6:d0:d4:9b:33
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical
wireless
configuration: broadcast=yes driver=ath10k_pci
driverversion=5.5.0-050500-generic
Re: [Touch-packages] [Bug 1864992] Please test proposed package
> Hello Paride, or anyone else affected, > > Accepted kmod into bionic-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.3 in > a few hours, and then in the -proposed repository. kmod (24-1ubuntu3.3) bionic; urgency=medium * d/p/verbose_missing_bin: drop this patch to avoid spurious missing file messages when running depmod -a for the first time in recent kernels (>= 5.3.x) (LP: #1864992) * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) -- Rafael David Tinoco Wed, 11 Mar 2020 19:37:06 + (k)rafaeldtinoco@bkmodissue:~$ apt-cache policy kmod kmod: Installed: 24-1ubuntu3.3 Candidate: 24-1ubuntu3.3 Version table: *** 24-1ubuntu3.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 24-1ubuntu3.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 24-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages (k)rafaeldtinoco@bkmodissue:~$ uname -a Linux bkmodissue 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (k)rafaeldtinoco@bkmodissue:~$ sudo rm /lib/modules/$(uname -r)/modules.builtin.bin (k)rafaeldtinoco@bkmodissue:~$ sudo depmod -a -F /boot/System.map-$(uname -r) (k)rafaeldtinoco@bkmodissue:~$ (k)rafaeldtinoco@bkmodissue:~$ uname -a Linux bkmodissue 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (k)rafaeldtinoco@bkmodissue:~$ sudo rm /lib/modules/$(uname -r)/modules.builtin.bin (k)rafaeldtinoco@bkmodissue:~$ sudo depmod -a -F /boot/System.map-$(uname -r) (k)rafaeldtinoco@bkmodissue:~$ ** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in kmod source package in Disco: Won't Fix Status in kmod source package in Eoan: Fix Committed Status in kmod source package in Focal: Fix Released Bug description: [Impact] * There is no impact to the end user but spurious error messages (tons of them) causing the perception that something really bad happened: Example of one of those tons of messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' [Test Case] * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin * sudo depmod -a -F /boot/System.map-$(uname -r) This will cause the spurious error messages because depmod -a -F won't have the "modules.builtin.bin" file created. This is a simulation of what the linux-modules postinst package does and an example of why the messages happen. [Regression Potential] * We are reverting a debian patch so we will be closer to upstream code base. * the change is about 2 different priority changes on verbosity, so biggest problem would be extra (or fewer) stdout/stderr messages (for scripts relying on them, for example). * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed to work fine. [Other Info] * Original Description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser',
Re: [Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'
> Hello Paride, or anyone else affected, > > Accepted kmod into eoan-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/kmod/26-1ubuntu1.1 in > a few hours, and then in the -proposed repository. Verification for eoan-proposed: (k)rafaeldtinoco@ekmodissue:~$ apt changelog kmod Get:1 https://changelogs.ubuntu.com kmod 26-1ubuntu1.1 Changelog [21.1 kB] Fetched 21.1 kB in 2s (10.4 kB/s) kmod (26-1ubuntu1.1) eoan; urgency=medium * d/p/verbose_missing_bin: drop this patch to avoid spurious missing file messages when running depmod -a for the first time in recent kernels (>= 5.3.x) (LP: #1864992) * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) -- Rafael David Tinoco Wed, 11 Mar 2020 19:32:52 + (k)rafaeldtinoco@ekmodissue:~$ apt-cache policy kmod kmod: Installed: 26-1ubuntu1.1 Candidate: 26-1ubuntu1.1 Version table: *** 26-1ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages 100 /var/lib/dpkg/status 26-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages (k)rafaeldtinoco@ekmodissue:~$ uname -a Linux ekmodissue 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux (k)rafaeldtinoco@ekmodissue:~$ sudo rm /lib/modules/$(uname -r)/modules.builtin.bin (k)rafaeldtinoco@ekmodissue:~$ sudo depmod -a -F /boot/System.map-$(uname -r) (k)rafaeldtinoco@ekmodissue:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864992 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in kmod source package in Disco: Won't Fix Status in kmod source package in Eoan: Fix Committed Status in kmod source package in Focal: Fix Released Bug description: [Impact] * There is no impact to the end user but spurious error messages (tons of them) causing the perception that something really bad happened: Example of one of those tons of messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' [Test Case] * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin * sudo depmod -a -F /boot/System.map-$(uname -r) This will cause the spurious error messages because depmod -a -F won't have the "modules.builtin.bin" file created. This is a simulation of what the linux-modules postinst package does and an example of why the messages happen. [Regression Potential] * We are reverting a debian patch so we will be closer to upstream code base. * the change is about 2 different priority changes on verbosity, so biggest problem would be extra (or fewer) stdout/stderr messages (for scripts relying on them, for example). * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed to work fine. [Other Info] * Original Description: During a Focal install from the ISO image several errors like: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin' are logged in curtin's install logs. The installed system boots and works fine, but the error is clearly something we want to get rid of. At first glance this seems related to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261 but the version of initramfs-tools in both the installer and installed system (checked with `chroot /target dpkg -l initramfs-tools` during the installation) is 0.136ubuntu1, which should contain Rafael's fix for that bug. I wonder if the update-initramfs diversion has a role here. I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperVersion: 1.439 DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
[Touch-packages] [Bug 1858412] Re: systemd vacuuming does not work for remote journals
** Changed in: systemd (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1858412 Title: systemd vacuuming does not work for remote journals Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Confirmed Bug description: systemd has an issue in regard to vacuuming remote journals: https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as this version still has this problem. Steps to reproduce on "Description: Ubuntu 18.04.3 LTS": root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M root@1:~# du -hs /var/log/journal/remote/ 8.6G /var/log/journal/remote/ Would it be possible to backport this trivial patch https://github.com/systemd/systemd/pull/13924 into 18.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
