coreos / coreos/coreos-assembler
systemd-userdb Mishandled
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 393
- Forks
- 193
- Avg merge
- 17h 6m
- Merged PRs (30d)
- 5
Description
Bug Report
If any users or groups are defined using the systemd-userdb JSON drop-in files in /usr/lib/userdb, the coreos-assembler is incorrectly generating a user.ign file during image creation that duplicates the settings and causes a failure.
Environment
What operating system is being used to run coreos-assembler? Docker
What operating system is being assembled? Variant of fedora-coreos-config with an extra overlay.d
Is coreos-assembler running in Podman or Docker? Podman
If Podman, is coreos-assembler running privileged or unprivileged? privileged
Expected Behavior
Putting files in /usr/lib/userdb/ should have no effect at all on the ignition file generated for the coreos-assembler output image.
Actual Behavior
A user.ign ignition file is being generated with a passwd section that duplicates the settings from the /usr/lib/userdb of the rootfs during image creation.
Reproduction Steps
- Add user and group JSON files for
systemd-userdbwith UID=1000, GID=1000 to the/usr/lib/userdb/folder via overlay. - Build a qcow2 image
- Attempt to run the qcow2 image in a VM
- See the dracut emergency shell ignition errors about creating the users/groups
Other Information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing image creation with JSON user and group files overlaid in /usr/lib/userdb, then inspect the generated user.ign and the image-build path that creates it. Done means files in /usr/lib/userdb no longer produce a duplicate passwd section and the resulting qcow2 image boots without ignition user or group errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100