-
Notifications
You must be signed in to change notification settings - Fork 124
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
Unable to set user password following documentation #322
Comments
The documentation for Fedora CoreOS does not necessarily apply to CentOS Stream. |
No problem with that but the Fedora CoreOS documentation doesn't tell on which OS the documented command actually works. |
Oh, I see your point. Yeah, that's a good point; thanks for the report. |
Looks like the documented commands works on Fedora 34 with the following package:
|
Running that command from a Fedora container might be the easiest workaround. |
Created a |
RHEL 8 ships a different implementation of mkpasswd that doesn't support modern hashes. For ease of use, just containerize mkpasswd. Fixes #322.
Describe the bug
Documentation for setting up a password for a user on coreos doesn't work for me.
I'm following: https://docs.fedoraproject.org/en-US/fedora-coreos/authentication/#_using_password_authentication.
It says:
I'm on CentOS Stream 8 which I used for the bastion of an OKD deployment. I run:
dnf provides "*/mkpasswd"
getting:Then I install it:
dnf install expect
. But running the suggested command:Reproduction steps
Steps to reproduce the behavior:
Expected behavior
documentation should provide exact steps to be able to set the password for coreos users
Actual behavior
can't setup a password for the user given existing documentation
Ignition config
Please attach your FCC or Ignition config used to provision your system. Be sure to sanitize any private data. If not using FCCT to generate your Ignition config, does the Ignition config pass validation using ignition-validate?
Additional information
Add any other information about the problem here.
The text was updated successfully, but these errors were encountered: