If I configure a local repository in the container `Server = file:///b`.
Then try `arch-nspawn /path/to/container`, it would expect that `/b` exist on the host.

Failed to stat /b: No such file or directory

arch-nspawn inserts `--bind=/b` to systemd-nspawn's arguments, probably since [1].

It seems that the issue mentioned in the commit ( FS#45882 ) could be workarounded by passing --bind-ro manually.
makechrootpkg (which wraps arch-nspawn) also provides `-d` and `-D` for additional bind mounts.

[1] https://git.archlinux.org/devtools.git/commit/?id=69112171e5de910331e46cf3f848866550125024

---

My use case is: I have local file:// repositories in the host somewhere like /home/user/custompkgs and configured as
file:///custompkgs in the container. The change mentioned above required the repo have the same paths.
I used --bind-ro=/home/user/custompkgs:/custompkgs or -D /home/user/custompkgs:/custompkgs in arch-nspawn and makechrootpkg respectively.