please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594849
Title:
systemd-nspawn: option
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
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
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
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594849
Title:
