Closed jerbmega closed 1 year ago
You have an rpm-ostree based container?
This may not be the best place to solve this problem.
Yes, it's a custom image I intend to boot off of. There are similar issues on this repo (#413 and #430) and I was advised this is the right place to file a bug for this workflow.
The package works properly when layering it over an existing installation, implying this is solely a container issue.
Then this is an rpm-ostree issue. Please file the issue there.
I'm closing this here as we don't ship ligthdm
in Silverblue.
Error opening directory `/var/lib/lightdm-data`: No such file or directory
This should be converted to a tmpfiles.d
config file instead of being manually created in the package.
I'll file an issue with rpm-ostree, thanks.
(I am still curious: are there any examples of rpm-ostree based containers generally available?)
@juhp You should checkout the great work from the https://ublue.it/ team :)
Describe the bug LightDM is not properly installed when added within a Containerfile. Adding
lightdm
in a Containerfile results in a build that succeeds, but cannot properly run LightDM, as the user is not made due to an error. I also get adbus-daemon
error within the container. I've reproduced this on both Fedora 37 and 38.I get the following error during build:
When running
lightdm --debug
in the resulting install, the following relevant debug output is noted:The package works properly when layering it over an existing installation, implying this is solely a container issue.
To Reproduce
rpm-ostree install lightdm
into a Containerfile. The build will succeed but will not run properly once deployed, with the above symptoms. This can be reproduced both via a local Podman build as well as Github Actions.