-
Notifications
You must be signed in to change notification settings - Fork 233
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
Suse integration #156
Suse integration #156
Conversation
if config[:platform] == 'opensuse' || config[:platform] == 'sles' | ||
userpw = <<-eos | ||
RUN if ! getent passwd #{username}; then useradd -d /home/#{username} -m -s /bin/bash #{username}; fi | ||
RUN echo #{username}:`perl -e 'print crypt("#{password}", "salt")'` | chpasswd -e |
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 doesn't seem to actually be required. Was there a reason you added it?
@coderanger thanks for your comment sles and opensuse do have a security policy that will deny the built in way to set the password. Its quite few months ago so i can't remember the exact name of the lib that is doing that... but on Suse machines the line
the kitchen create finishes but you can't connect with ssh provisioner afterwards. The line you commented on creates a way around the password verification with encrypting the password before piping it into chpasswd I hope ist was understandable. :) |
Hi guys, |
Another interested user, not sure if this is going to be managed anytime soon but open to help. Thanks! |
I'm going to close this out at this point since we have opensuse and opensuse leap in the case statements as well as testing. Feel free to open a new PR if you think something is still missing. |
We work mainly with SLES and OpenSUSE OS-Images, so we need to use them as kitchen-docker baseimage for testing purposes.
This PR enables kitchen-docker to work on Suse-Based-Images properly.
Tested with SLES12 and OpenSUSE 13.2