-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LightDM doesn't properly install within a container #4369
Comments
Notes from investigation in the parent ticket:
This should be converted to a
It's unclear to me why this would fail in rpm-ostree while this works in the classic RPM case. |
It looks like the template Containerfile I started from deletes the contents of /var and /tmp from the container before running a commit, so that much isn't an ostree issue. |
I've updated my comment. It's expected that /var & /tmp are cleared out as they are not part of the ostree commit. Packages should use systemd tmpfiles.d config files to setup files in those directories. |
Mobile misclick, sorry |
I believe this is implied by `--system` anyways, but at least one spec file was discovered to be using this in the wild. Closes: coreos#4369
I believe this is implied by `--system` anyways, but at least one spec file was discovered to be using this in the wild. Closes: coreos#4369
I've been advised to move this here from fedora-silverblue/issue-tracker#452.
Host system details
No "host" in this case, this is in an OCI build.
Expected vs actual behavior
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.The package works properly when layering it over an existing installation, implying this is solely a container issue.
I get the following error during build:
When running
lightdm --debug
in the resulting install, the following relevant debug output is noted:Expected:
The LightDM user should be properly set up during the build process.
Steps to reproduce it
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.The text was updated successfully, but these errors were encountered: