Closed TH3-S4LM0N closed 8 months ago
Your base image is old. We need more details to be able to diagnose.
We need more details to be able to diagnose.
Ok, I created a full new vm with the latest image (37.20230117.0
). Then I ran sudo systemctl disable gdm
, rebooted and was greeted by a terminal as expected. I re-enabled it, rebooted and gdm came up. I rebased to this image I made to display this with rpm-ostree rebase ostree-unverified-registry:ghcr.io/th3-s4lm0n/sb-systemd-gdm-bug
. Note that I don't think this image would be based off the latest image, but if i pull from silverblue:latest
it errors out that the manifest is unknown. Anyway then I reboot and get the black screen.
You can try with https://quay.io/repository/fedora-ostree-desktops/silverblue?tab=tags which should be fresher.
Exact same thing with FROM quay.io/fedora-ostree-desktops/silverblue:37.20230118.0.a4bd7c6a
.
Looks like this is related to building in unified core mode (which is how those images are made).
This will be fixed by https://pagure.io/workstation-ostree-config/pull-request/246.
In the meantime, you can manually enable the missing units:
$ systemctl enable getty@.service
I'll likely backport this to the test images.
This is fixed in F39.
Description
Disabling GDM in a OCI container image causes a black screen on boot, but works as intended when run on the actual installed os.
Reproduce
RUN systemctl disable gdm
Expected Behavior
A terminal.
OS version:
Running in a Qemu/KVM virtual machine on Arch Linux for testing if it matters.