MisthiosandClaude Opus 5.5
4f71d350fa
Build containers / Compute changes (pull_request) Successful in 2s
Build containers / fedora-remote (44) (pull_request) Successful in 11m9s
Build containers / fedora-cosmic (rawhide) (pull_request) Successful in 12m8s
Build containers / fedora-cosmic (44) (pull_request) Successful in 14m20s
Build containers / fedora-intune (44) (pull_request) Canceled after 10m35s
Build containers / fedora-intune-himmelblau (44) (pull_request) Canceled after 9m41s
Build containers / Prune old releases and tags (pull_request) Skipped
Fixes found by building and inspecting the image: - Select the Intune authselect profile with-altfiles. Without it system users in /usr/lib/passwd (gdm, pipewire, mdatp) do not resolve and the login screen never starts. The build now fails if gdm does not resolve. - Ship /opt as a plain directory (opt-usrlocal: root). Defender installs to /opt/microsoft/mdatp and keeps state in /var/opt/microsoft/mdatp; with the default /opt -> /var/opt symlink those were the same read-only directory. rpm-ostree still relocates /opt content to /usr/lib/opt, so finalize.d/60-opt-links links it back (only for images where /opt is a directory; fedora-cosmic/remote are unaffected). - Run Defender's %post on first boot (mdatp-firstboot.service): in a compose /var is read-only and the machine GUID/state must not be shared. mdatp.service waits for it. New image fedora-intune-himmelblau: the same workstation with Entra ID sign-in through Himmelblau (Community Nightly packages), which joins the device at the first sign-in and enrolls it in Intune (apply_policy) instead of the Microsoft Intune app. Workstation, Edge and Defender manifests move to images/shared so both images use them; build.sh copies images/shared/*.yaml and CI builds both images in one matrix job. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
18 lines
594 B
Bash
18 lines
594 B
Bash
#!/usr/bin/env bash
|
|
# Finish the Defender (mdatp) install on first boot by running the package's
|
|
# own %post, saved at build time: it creates the machine GUID, state, logs and
|
|
# definitions database under /var and then enables and starts mdatp.service.
|
|
set -euo pipefail
|
|
|
|
MARKER=/var/lib/mdatp-firstboot.done
|
|
|
|
[[ -f "${MARKER}" ]] && exit 0
|
|
|
|
# mdatp.service only starts once the marker exists (10-firstboot.conf), and the
|
|
# %post starts it, so create the marker first and drop it again on failure.
|
|
touch "${MARKER}"
|
|
if ! bash /usr/libexec/mdatp-postinst 1; then
|
|
rm -f "${MARKER}"
|
|
exit 1
|
|
fi
|