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
/etc/bash
being used to check nvm --version
#21
Comments
I've just run it myself on a clean 18.04 instance with the .bashrc as a default without any issues. F.Y.I Documentation has recently been added/updated to describe why running role as Root is bad and makes suggestions for what to do if running the role with different user profiles e.g. Are you doing anything special with users, user homes, user permissions? |
Huh, yeah, I read through the stuff about running as root, and I'm not. Lemme pare down what I have and put it up here. |
Output (skipping Vagrant lines):
|
And one small thing that might looks weird - I used to install this role directly from github because the Ansible Galaxy version was behind, hence why the role is referenced as |
Ok, I've finally been able to recreate the issue. I had to download a fresh version of the role. Let me look into it and I'll get back to you. |
Actually yeah, that makes sense - I only started seeing it after I did a big force-upgrade of all my libraries. Worked perfectly before that. |
Ok, I've pushed a change here 5abb5d5 You can easily test if it works by changing branches: or by changing line 50 in the mvn.yml file from
to
If it works, let me know. |
Works perfectly! |
Also, I am stealing your practice of having a reasonably named "main" tasks file and having |
Thanks for the help. |
Describe the bug
Expected behavior
To Reproduce
Attempt to run the role against a fresh Ubuntu 18.04 instance. I have tried with and without setting
nvm_profile: ".bashrc"
and get the same error.Shell [e.g. Bash, Dash, ksh, tcsh, zsh]
Bash
Desktop (please complete the following information):
Debugging output
Additional context
I did some digging around, trying to see why it was using
/etc/bash
, and it appears the role is running the following task:Breaking that conditional down a little further, I found that:
But
Which is weird, because:
I'm not sure why casting
/bin/bash
to bool is False, but it looks like that's what's causing that conditional to be true, and what's causing the weird bash location that's tripping up my install. Thoughts?The text was updated successfully, but these errors were encountered: