-
Notifications
You must be signed in to change notification settings - Fork 669
quick fix to run archinstall and enable systemd services #3815
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
quick fix to run archinstall and enable systemd services #3815
Conversation
|
There was a similar suggestion on the Arch GitLab: https://gitlab.archlinux.org/archlinux/packaging/packages/systemd/-/issues/54#note_322382 |
|
The fix partially works, in that I am able to get Arch installed using archinstall... but still seems like something is broken. If I arch-chroot into the system after the install and run my post-install script, any systemctl command is failing with:
This worked before the systemd update. |
There's an underlying issue in systemd: systemd/systemd#39021 |
YHNdnzj
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that I've updated the PR description to highlight it's not a systemd bug after all. arch-chroot needs to be fixed and the systemd change just revealed the flaw there.
|
|
||
| try: | ||
| self.arch_chroot(f'systemctl enable {service}') | ||
| SysCommand(f'systemctl --root={self.target} enable {service}') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This operates on a chroot in a way native to systemd tools and should be done regardless of arch-chroot working or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to remember that we're on Arch Linux and the recommended way (by our own Wiki) is/was to configure the system using arch-chroot, generally speaking.
It's unfortunate that this issue happens, and we'll try to work around it.
But we wish to use native tooling with default values wherever possible and not use workarounds or too many custom parameters (again, if possible).
PR Description:
Just inserted a direct call to SysCommand instead of self.arch_chroot, with the flag --root={self.target}.
This fixed the issue, at least for me.
Tests and Checks