[Touch-packages] [Bug 1979139] [NEW] apt-get update fails inside docker container
Public bug reported: A docker image built with "debootstrap jammy" fails when running "apt- get update". 1) lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 2) # apt-cache policy docker.io docker.io: Installed: 19.03.8-0ubuntu1.20.04.1 Candidate: 20.10.7-0ubuntu5~20.04.2 Version table: 20.10.7-0ubuntu5~20.04.2 500 500 http://mirror.localnet:8055/ubuntu-security focal-security/universe amd64 Packages *** 19.03.8-0ubuntu1.20.04.1 100 100 /var/lib/dpkg/status 19.03.8-0ubuntu1 500 500 http://mirror.localnet:8055/ubuntu focal/universe amd64 Packages # docker run --rm -ti ubuntu:jammy apt-cache policy apt apt: Installed: 2.4.5 Candidate: 2.4.5 Version table: *** 2.4.5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) I would expect, that "apt-get update" updates the package lists, as in # docker run --rm -ti ubuntu:focal apt-get update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Fetched 506 kB in 1s (464 kB/s) Reading package lists... Done 4) Instead, it fails with # docker run --rm -ti ubuntu:jammy apt-get update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C Reading package lists... Done W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg are ignored as the file is not readable by user '_apt' executing apt-key. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C W: Some index files failed to download. They have been ignored, or old ones used instead. 5) To reproduce: # mkdir jammy-jellyfish # debootstrap jammy jammy-jellyfish ... # tar -C jammy-jellyfish -c . | docker import - ubuntu:jammy # docker run --rm -ti ubuntu:jammy apt-get update Doing the same with focal, works as expected: # mkdir focal-fossa # debootstrap focal focal-fossa ... # tar -C focal-fossa -c . | docker import - ubuntu:focal # docker run --rm -ti ubuntu:focal apt-get update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Fetched 506 kB in 1s (963 kB/s) Reading package lists... Done ** 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/1979139 Title: apt-get update fails inside docker container Status in apt package in Ubuntu: New Bug description: A docker image built with "debootstrap jammy" fails when running "apt- get update". 1) lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 2) # apt-cache policy docker.io docker.io: Installed: 19.03.8-0ubuntu1.20.04.1 Candidate: 20.10.7-0ubuntu5~20.04.2 Version table: 20.10.7-0ubuntu5~20.04.2 500 500 http://mirror.localnet:8055/ubuntu-security focal-security/universe amd64 Packages *** 19.03.8-0ubuntu1.20.04.1 100 100 /var/lib/dpkg/status 19.03.8-0ubuntu1 500 500 http://mirror.localnet:8055/ubuntu focal/universe amd64 Packages # docker run --rm -ti ubuntu:jammy apt-cache policy apt apt: Installed: 2.4.5 Candidate: 2.4.5 Version table: *** 2.4.5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 3) I would expect, that "apt-get update" updates the package lists, as in # docker run --rm -ti ubuntu:focal apt-get update Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Get:2 http://archive.ubuntu.com/ubuntu focal/main Translation-en [506 kB] Fetched 506 kB in 1s (464 kB/s) Reading package lists... Done 4) Instead, it fails with # docker run --rm -ti ubuntu:jammy apt-get update Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease The following signatures couldn't be verified because the public key is
[Touch-packages] [Bug 1822462] [NEW] apt-get reports signature problem when /tmp is full
Public bug reported: 1) Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2) apt: Installed: 1.6.10 Candidate: 1.6.10 Version table: *** 1.6.10 100 100 /var/lib/dpkg/status 3) I would expect a helpful error message, saying there's not enough disk space, or maybe even pointing at the /tmp partition. 4) My /tmp partition was full, when I tried `apt-get update`. It failed with the following errors: Get:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Err:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic_InRelease into data and signature failed Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Err:2 http://security.ubuntu.com/ubuntu bionic-security InRelease Splitting up /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_bionic-security_InRelease into data and signature failed Get:3 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB] Err:3 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-updates_InRelease into data and signature failed Get:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Err:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-backports_InRelease into data and signature failed Reading package lists... Done W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic InRelease: Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic_InRelease into data and signature failed E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://security.ubuntu.com/ubuntu bionic-security InRelease: Splitting up /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_bionic-security_InRelease into data and signature failed E: The repository 'http://security.ubuntu.com/ubuntu bionic-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease: Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-updates_InRelease into data and signature failed E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease: Splitting up /var/lib/apt/lists/partial/de.archive.ubuntu.com_ubuntu_dists_bionic-backports_InRelease into data and signature failed E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. The hint at unsigned repositories is misleading and it took quite some time to figure out the real problem. Therefore, I would expect an error message pointing at the real culprit, which in this case was missing disk space. --- After removing files from /tmp, apt-get update succeeds as expected: Get:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:2 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Get:4 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Get:5 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1.019 kB] Get:6 http://de.archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:7 http://de.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [9.184 B] Get:8 http://de.archive.ubuntu.com/ubuntu bionic/restricted Translation-en [3.584 B] Get:9 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8.570 kB] Get:10 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [284 kB] Get:11 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [104 kB] Get:12 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [4.296 B] Get:13 http://security.ubuntu.com/ubuntu bionic-security/restricted Translation-en [2.192 B] Get:14 http://de.archive.ubuntu.com/ubuntu bionic/universe
[Touch-packages] [Bug 1689660] [NEW] systemd-fsckd busy spawning fsck
Public bug reported: I rebooted my laptop after a crash. Fsck couldn't repair the /var partition, so I was greeted with "Welcome to Emergency!" and the request to look at `journalctl -xb`. After logging in, and journalctl telling me about the broken /var partition, I tried fsck /dev/mapper/vg0-var which immediately returned with a message stating that /dev/mapper/vg0-var is busy. Looking at the processes with `ps aux | grep fsck` gave - systemd-fsckd - /sbin/fsck /dev/mapper/vg0-var - fsck.ext2 /dev/mapper/vg0-var Trying to kill `fsck.ext2` or `fsck` was futile, because `fsck` was dying and restarting faster, than I could look at the process list. Killing `systemd-fsckd` finally ended the busy loop. But still, I couldn't check my /var partition, because now systemd has mounted my /var partition, even though it told me before, it was in need of repair. After unmounting /var, I could finally do the much needed `fsck /dev/mapper/vg0-var`. --- I would expect 1. systemd-fsck stop restarting fsck, when it was aware, that it must be checked manually 2. systemd *not* mount an unchecked file system, especially when systemd-fsckd stopped with an error or was killed --- Description:Ubuntu 16.04 LTS Release:16.04 --- systemd: Installed: 229-4ubuntu10 Candidate: 229-4ubuntu16 Version table: 229-4ubuntu16 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages --- ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1689660 Title: systemd-fsckd busy spawning fsck Status in systemd package in Ubuntu: New Bug description: I rebooted my laptop after a crash. Fsck couldn't repair the /var partition, so I was greeted with "Welcome to Emergency!" and the request to look at `journalctl -xb`. After logging in, and journalctl telling me about the broken /var partition, I tried fsck /dev/mapper/vg0-var which immediately returned with a message stating that /dev/mapper/vg0-var is busy. Looking at the processes with `ps aux | grep fsck` gave - systemd-fsckd - /sbin/fsck /dev/mapper/vg0-var - fsck.ext2 /dev/mapper/vg0-var Trying to kill `fsck.ext2` or `fsck` was futile, because `fsck` was dying and restarting faster, than I could look at the process list. Killing `systemd-fsckd` finally ended the busy loop. But still, I couldn't check my /var partition, because now systemd has mounted my /var partition, even though it told me before, it was in need of repair. After unmounting /var, I could finally do the much needed `fsck /dev/mapper/vg0-var`. --- I would expect 1. systemd-fsck stop restarting fsck, when it was aware, that it must be checked manually 2. systemd *not* mount an unchecked file system, especially when systemd-fsckd stopped with an error or was killed --- Description: Ubuntu 16.04 LTS Release: 16.04 --- systemd: Installed: 229-4ubuntu10 Candidate: 229-4ubuntu16 Version table: 229-4ubuntu16 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1689660/+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 738617] Re: package should not depend on wpasupplicant
This bug is still valid in Xenial 16.04. My system is connected via LAN and doesn't have a wireless card installed. Because of the dependency, wpa_cli is run on each suspend/resume cycle and fails of course. There is no technical reason for this dependency, and a recommendation is strong enough to satisfy the perceived need, while still allowing to get rid of wpasupplicant. I consider shifting the decision to Debian maintainers a dummy argument. It would not be the first time, where changes flow from Ubuntu to Debian. -- 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/738617 Title: package should not depend on wpasupplicant Status in network-manager package in Ubuntu: Won't Fix Bug description: Binary package hint: network-manager I think the network-manager package should recommend the wpasupplicant but not depend on it. Basically, on old hardware which doesn't use a wireless network, it could help to uninstall wpasupplicant. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: network-manager 0.8-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-30.59-generic 2.6.32.29+drm33.13 Uname: Linux 2.6.32-30-generic i686 Architecture: i386 CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Date: Sun Mar 20 10:47:00 2011 Gconf: InstallationMedia: Xubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) IpRoute: 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.11 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.0.254 dev eth0 proto static IwConfig: lono wireless extensions. eth0 no wireless extensions. Keyfiles: Error: [Errno 2] Aucun fichier ou dossier de ce type ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash RfKill: SourcePackage: network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/738617/+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 1594849] Re: systemd-nspawn: option --overlay not working
It seems, you're right with the final path component in --overlay. This is the absolute path *inside* the container. I looked into nspawn's source code and the options is interpreted as follows --overlay=lo1:lo2:up:dest lo1 and lo2 are lower directories, up is the upper directory in overlayfs terms, and all are absolute host directory paths. dest is the where the overlayfs is mounted inside the container's root directory. In order to use --overlay, I have to say --overlay=/path/to/xenial/usr:/path/to/apache/usr:/path/to/container/usr:/usr and repeat this for /etc, /bin, /sbin, /lib, /lib64, /var. So --overlay seems to work, sort of. Anyway, thank you for pushing me into the right direction. I think, I'll stay with my workaround, overlay mounting the base directories upfront, and then nspawning the container on the resulting root directory. -- 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/1594849 Title: systemd-nspawn: option --overlay not working Status in systemd package in Ubuntu: Confirmed Bug description: I have a directory with a minimal Xenial installation, which I want to share among several containers. I also have a directory with just Apache and its dependencies installed. systemd-nspawn has an option --overlay to "Combine multiple directory trees into one overlay file system and mount it into the container." Neither `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache -D /path/to/container` nor `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache:/path/to/container -D /path/to/container` works as expected. Both report an error "Directory /path/to/container doesn't look like it has an OS tree. Refusing.". Of course, it doesn't have an OS tree, this is what the base overlays are for. Looking at the source code, creating a subdirectory /path/to/container/usr works around this. But now it complains about "Failed to create directory /path/to/container/sys/fs/selinux: Read- only file system" twice, then about a missing timezone, and finally aborts with Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory Doing this manually instead, works fine: mount -t overlay -o lowerdir=/path/to/apache:/path/to/xenial,upperdir=/path/to/container,workdir=/path/to/workdir none /path/to/container systemd-nspawn -D /path/to/container 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) systemd-container: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 3) I expect systemd-nspawn to mount an overlayfs with the provided directories and then start the container with all the directories combined. 4) systemd-nspawn complains - Directory /path/to/container doesn't look like it has an OS tree. Refusing. and after working around this (among other irrelevant error messages) - Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594849/+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 1594849] Re: systemd-nspawn: option --overlay not working
Tank you for pointing to the feature request and the discussion. --- >From the man page (https://www.freedesktop.org/software/systemd/man /systemd-nspawn.html#--overlay=): >For details about overlay file systems, see overlayfs.txt. Which links to https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt, and there it is clearly defined, how overlayfs works. So whatever nspawn does, it doesn't seem to conform to Linux kernel's notion of overlay file system. -- 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/1594849 Title: systemd-nspawn: option --overlay not working Status in systemd package in Ubuntu: Confirmed Bug description: I have a directory with a minimal Xenial installation, which I want to share among several containers. I also have a directory with just Apache and its dependencies installed. systemd-nspawn has an option --overlay to "Combine multiple directory trees into one overlay file system and mount it into the container." Neither `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache -D /path/to/container` nor `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache:/path/to/container -D /path/to/container` works as expected. Both report an error "Directory /path/to/container doesn't look like it has an OS tree. Refusing.". Of course, it doesn't have an OS tree, this is what the base overlays are for. Looking at the source code, creating a subdirectory /path/to/container/usr works around this. But now it complains about "Failed to create directory /path/to/container/sys/fs/selinux: Read- only file system" twice, then about a missing timezone, and finally aborts with Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory Doing this manually instead, works fine: mount -t overlay -o lowerdir=/path/to/apache:/path/to/xenial,upperdir=/path/to/container,workdir=/path/to/workdir none /path/to/container systemd-nspawn -D /path/to/container 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) systemd-container: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 3) I expect systemd-nspawn to mount an overlayfs with the provided directories and then start the container with all the directories combined. 4) systemd-nspawn complains - Directory /path/to/container doesn't look like it has an OS tree. Refusing. and after working around this (among other irrelevant error messages) - Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594849/+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 1594849] [NEW] systemd-nspawn: option --overlay not working
Public bug reported: I have a directory with a minimal Xenial installation, which I want to share among several containers. I also have a directory with just Apache and its dependencies installed. systemd-nspawn has an option --overlay to "Combine multiple directory trees into one overlay file system and mount it into the container." Neither `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache -D /path/to/container` nor `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache:/path/to/container -D /path/to/container` works as expected. Both report an error "Directory /path/to/container doesn't look like it has an OS tree. Refusing.". Of course, it doesn't have an OS tree, this is what the base overlays are for. Looking at the source code, creating a subdirectory /path/to/container/usr works around this. But now it complains about "Failed to create directory /path/to/container/sys/fs/selinux: Read-only file system" twice, then about a missing timezone, and finally aborts with Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory Doing this manually instead, works fine: mount -t overlay -o lowerdir=/path/to/apache:/path/to/xenial,upperdir=/path/to/container,workdir=/path/to/workdir none /path/to/container systemd-nspawn -D /path/to/container 1) Description:Ubuntu 16.04 LTS Release:16.04 2) systemd-container: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 3) I expect systemd-nspawn to mount an overlayfs with the provided directories and then start the container with all the directories combined. 4) systemd-nspawn complains - Directory /path/to/container doesn't look like it has an OS tree. Refusing. and after working around this (among other irrelevant error messages) - Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1594849 Title: systemd-nspawn: option --overlay not working Status in systemd package in Ubuntu: New Bug description: I have a directory with a minimal Xenial installation, which I want to share among several containers. I also have a directory with just Apache and its dependencies installed. systemd-nspawn has an option --overlay to "Combine multiple directory trees into one overlay file system and mount it into the container." Neither `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache -D /path/to/container` nor `systemd-nspawn --overlay=/path/to/xenial:/path/to/apache:/path/to/container -D /path/to/container` works as expected. Both report an error "Directory /path/to/container doesn't look like it has an OS tree. Refusing.". Of course, it doesn't have an OS tree, this is what the base overlays are for. Looking at the source code, creating a subdirectory /path/to/container/usr works around this. But now it complains about "Failed to create directory /path/to/container/sys/fs/selinux: Read- only file system" twice, then about a missing timezone, and finally aborts with Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory Doing this manually instead, works fine: mount -t overlay -o lowerdir=/path/to/apache:/path/to/xenial,upperdir=/path/to/container,workdir=/path/to/workdir none /path/to/container systemd-nspawn -D /path/to/container 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) systemd-container: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 3) I expect systemd-nspawn to mount an overlayfs with the provided directories and then start the container with all the directories combined. 4) systemd-nspawn complains - Directory /path/to/container doesn't look like it has an OS tree. Refusing. and after working around this (among other irrelevant error messages) - Creating mount point for overlay /path/to/container/path/to/apache failed: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1594738] [NEW] systemctl not working inside chroot
Public bug reported: AFAIU, Ubuntu switched to systemd as its service management system. Therefore I expect it to start services even in a chroot environment. Using "service apache2 start" instead works without any problems. 1) Description:Ubuntu 16.04 LTS Release:16.04 2) systemd: Installed: 229-4ubuntu4 Candidate: 229-4ubuntu6 Version table: 229-4ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) "systemctl start apache2" should start Apache webserver. 4) "systemctl start apache2" does not start Apache webserver. Instead it says >Running in chroot, ignoring request. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1594738 Title: systemctl not working inside chroot Status in systemd package in Ubuntu: New Bug description: AFAIU, Ubuntu switched to systemd as its service management system. Therefore I expect it to start services even in a chroot environment. Using "service apache2 start" instead works without any problems. 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) systemd: Installed: 229-4ubuntu4 Candidate: 229-4ubuntu6 Version table: 229-4ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) "systemctl start apache2" should start Apache webserver. 4) "systemctl start apache2" does not start Apache webserver. Instead it says >Running in chroot, ignoring request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594738/+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 1594505] Re: No WLAN after suspend/resume
** Description changed: - After resume my laptop loses WLAN connectivity. I can restore WLAN - connectivity by restarting network-manager with + After resume my laptop loses sometimes WLAN connectivity. I can restore + WLAN connectivity by restarting network-manager with # systemctl restart network-manager 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) network-manager: - Installed: 1.1.93-0ubuntu4 - Candidate: 1.2.0-0ubuntu0.16.04.2 - Version table: - 1.2.0-0ubuntu0.16.04.2 500 - 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages - *** 1.1.93-0ubuntu4 500 - 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.1.93-0ubuntu4 + Candidate: 1.2.0-0ubuntu0.16.04.2 + Version table: + 1.2.0-0ubuntu0.16.04.2 500 + 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + *** 1.1.93-0ubuntu4 500 + 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status 3) After resume, I expect to be able to use WLAN. 4) After resume, there is no WLAN available -- 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/1594505 Title: No WLAN after suspend/resume Status in network-manager package in Ubuntu: New Bug description: After resume my laptop loses sometimes WLAN connectivity. I can restore WLAN connectivity by restarting network-manager with # systemctl restart network-manager 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.2.0-0ubuntu0.16.04.2 Version table: 1.2.0-0ubuntu0.16.04.2 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.1.93-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) After resume, I expect to be able to use WLAN. 4) After resume, there is no WLAN available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594505/+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 1594505] [NEW] No WLAN after suspend/resume
Public bug reported: After resume my laptop loses WLAN connectivity. I can restore WLAN connectivity by restarting network-manager with # systemctl restart network-manager 1) Description:Ubuntu 16.04 LTS Release:16.04 2) network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.2.0-0ubuntu0.16.04.2 Version table: 1.2.0-0ubuntu0.16.04.2 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.1.93-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) After resume, I expect to be able to use WLAN. 4) After resume, there is no WLAN available ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1594505 Title: No WLAN after suspend/resume Status in network-manager package in Ubuntu: New Bug description: After resume my laptop loses WLAN connectivity. I can restore WLAN connectivity by restarting network-manager with # systemctl restart network-manager 1) Description: Ubuntu 16.04 LTS Release: 16.04 2) network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.2.0-0ubuntu0.16.04.2 Version table: 1.2.0-0ubuntu0.16.04.2 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.1.93-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) After resume, I expect to be able to use WLAN. 4) After resume, there is no WLAN available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1594505/+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
