[Touch-packages] [Bug 1616939] [NEW] dbus.conf tmpfiles.d file dont populate /var/lib/dbus
Public bug reported: If I try to start a system without /var or with volatile one,the service "Create Volatile Files and Directories" fails with systemd-tmpfiles[23]: symlink(/etc/machine-id, /var/lib/dbus/machine-id) failed: No such file or directory If I add the line: d /var/lib/dbus 0755 - - - to /lib/tmpfiles.d/dbus.conf everything works. --- lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 apt-cache policy dbus dbus: Installed: 1.10.6-1ubuntu3 Candidate: 1.10.6-1ubuntu3 Version table: *** 1.10.6-1ubuntu3 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Description changed: If I try to start a system without /var or with volatile one,the service "Create Volatile Files and Directories" fails with systemd-tmpfiles[23]: symlink(/etc/machine-id, /var/lib/dbus/machine-id) failed: No such file or directory If I add the line: d /var/lib/dbus 0755 - - - to /lib/tmpfiles.d/dbus.conf everything works. + + lsb_release -rd + Description:Ubuntu 16.04.1 LTS + Release:16.04 + + apt-cache policy dbus + dbus: + Installed: 1.10.6-1ubuntu3 + Candidate: 1.10.6-1ubuntu3 + Version table: + *** 1.10.6-1ubuntu3 500 + 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status ** Description changed: If I try to start a system without /var or with volatile one,the service "Create Volatile Files and Directories" fails with systemd-tmpfiles[23]: symlink(/etc/machine-id, /var/lib/dbus/machine-id) failed: No such file or directory If I add the line: d /var/lib/dbus 0755 - - - to /lib/tmpfiles.d/dbus.conf everything works. + --- lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 apt-cache policy dbus dbus: - Installed: 1.10.6-1ubuntu3 - Candidate: 1.10.6-1ubuntu3 - Version table: - *** 1.10.6-1ubuntu3 500 - 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.10.6-1ubuntu3 + Candidate: 1.10.6-1ubuntu3 + Version table: + *** 1.10.6-1ubuntu3 500 + 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1616939 Title: dbus.conf tmpfiles.d file dont populate /var/lib/dbus Status in dbus package in Ubuntu: New Bug description: If I try to start a system without /var or with volatile one,the service "Create Volatile Files and Directories" fails with systemd-tmpfiles[23]: symlink(/etc/machine-id, /var/lib/dbus/machine- id) failed: No such file or directory If I add the line: d /var/lib/dbus 0755 - - - to /lib/tmpfiles.d/dbus.conf everything works. --- lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 apt-cache policy dbus dbus: Installed: 1.10.6-1ubuntu3 Candidate: 1.10.6-1ubuntu3 Version table: *** 1.10.6-1ubuntu3 500 500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1616939/+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
Ok, I'm misunderstanding overlay option. I think that you too. In your example "systemd-nspawn --overlay=/path/to/xenial:/path/to/apache:/path/to/container -D /path/to/container" really the last path of overlay option is path INSIDE container. So systemd-nspawn refuse to init the container because /path/to/container is actually empty. Anyways there is some request in systemd to support something like --overlay=/path/to/xenial:/path/to/apache:/ and get overlay mounted as rootfs of the container. I've written some topic in systemd-devel list asking for suggestions: https://lists.freedesktop.org/archives/systemd-devel/2016-August/037355.html Also a github issue asking for rootfs support: https://github.com/systemd/systemd/issues/3847 ** Bug watch added: github.com/systemd/systemd/issues #3847 https://github.com/systemd/systemd/issues/3847 -- 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
Neither overlay working here. I think that the root problem is systemd- nspawn never mounts the overlay. Please, can you can check it by defining --overlay and -D to different dirs and then check mounts in host? Is this behaviour correct? -- 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
