shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-10 05:18:17 +03:00
Code

portable: document /etc/machine-id and /etc/resolv.conf

Browse Source 
… requirement for portable service images.

systemd will mount the host machine-id and resolv.conf at these
locations, so for read-only images these must exist in the image,
because they can't be created.
This commit is contained in:
Дамјан Георгиевски 2019-01-31 14:28:59 +01:00 committed by Lennart Poettering
parent 16a81874e0
commit 6f61b14d53
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/PORTABLE_SERVICES.md
View File

@ -89,8 +89,9 @@ If you have portable service image, maybe in a raw disk image called
This command does the following:
1. It dissects the image, checks and validates the `/etc/os-release` data of
the image, and looks for all included unit files.
1. It dissects the image, checks and validates the `/etc/os-release`
(or `/usr/lib/os-release`, see below) data of the image, and looks for
all included unit files.
2. It copies out all unit files with a suffix of `.service`, `.socket`,
`.target`, `.timer` and `.path`. whose name begins with the image's name
@ -170,8 +171,11 @@ requirements are made for an image that can be attached/detached with
image. (The implementation will check a couple of other paths too, but it's
recommended to use these two paths.)
4. The image must contain an os-release file, either in /etc/os-release or
/usr/lib/os-release. The file should follow the standard format.
4. The image must contain an os-release file, either in `/etc/os-release` or
`/usr/lib/os-release`. The file should follow the standard format.
5. The image must contain the files `/etc/resolv.conf` and `/etc/machine-id`
(empty files are ok), they will be bind mounted from the host at runtime.
Note that generally images created by tools such as `debootstrap`, `dnf
--installroot=` or `mkosi` qualify for all of the above in one way or