From 7a4576eed532960f65ed64a2e6e767d95e599b5f Mon Sep 17 00:00:00 2001 From: askpng <81590263+askpng@users.noreply.github.com> Date: Sat, 26 Jul 2025 20:11:51 +0700 Subject: [PATCH] docs(os-release): Add note about module placement (#423) * docs(os-release): Add note about module placement Modifying `ID` may cause failures in identification and installation of COPR packages during the build process, and is ideally placed later in the recipe. * fix: use starlight note format Co-authored-by: Gerald Pinder * fix: minor rephrasements * docs: add more details to suggestion --------- Co-authored-by: xyny <60004820+xynydev@users.noreply.github.com> Co-authored-by: Gerald Pinder --- modules/os-release/README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/modules/os-release/README.md b/modules/os-release/README.md index cd77c24..865ee93 100644 --- a/modules/os-release/README.md +++ b/modules/os-release/README.md @@ -1,6 +1,10 @@ # **`os-release` Module** The `os-release` module offers a way to modify and set values in the [`/etc/os-release`](https://www.freedesktop.org/software/systemd/man/latest/os-release.html) file in your image. This file contains metadata about the running Linux operating system and is read by various programs. + +:::note +Modifying the `ID` value within `/etc/os-release` can cause COPR package identification and installation failures during the build process. When changing the `ID`, you should always set `ID_LIKE` to the type of base image you are using, ex. `ID_LIKE: fedora`. Errors from setting the `ID` may also be alleviated by running the module at the end of the build process, but beware that those errors would still be present in images derived from your image. +::: ## Example