Closed a-w-1806 closed 3 weeks ago
Ah dang, yep. provision.sh
assumes GNU sed. Sorry, I just broke that when I added something to make sure the right version of Ansible is installed (in 35d204d3e0b8486a9ff7edf14e08eda7ad768d90)! I'll just revert it for now, hopefully that'll get provision.sh
working for you again. Perhaps that sed command can be made more compatible with more versions of sed.
Yep I am using macOS so that might be the reason?
Do you know how to tweak that sed line to make it compatible with yours? Maybe it's BSD sed if it's on macOS.
Unfortunately no I am by no means a power sed
user 😞
No worries, I think I got it. Please try updating your clone, see if it works now.
Fixed in 35d204d3e0b8486a9ff7edf14e08eda7ad768d90, hopefully.
Thanks for the quick response! I am now seeing this:
❯ ./provision.sh
ERROR: Ansible core 2.16.1 or later required. Unable to determine version.
However:
❯ ansible --version
ansible [core 2.17.0]
...
Uff, yeah, that was super naive of me to think sort -V
would be portable (I bet that's what's breaking).
I know how to fix that bug in the version check for macOS, but it looks like you'll still need a more recent Ansible core (note the mention of version 2.16.1
in provision.sh
). Will you figure out how to upgrade Ansible core, and I'll fix the version check for macOS in provision.sh
?
🤔 I think I am having the latest ansible
from Homebrew already. 2.17.0 is already later than 2.16.1 right?
Whoops, indeed, my bad. Does provision.sh
get farther along for you now?
And yes I think this is expected as I haven't modified my config file yet:
❯ ./provision.sh
ssh: Could not resolve hostname mario_server: nodename nor servname provided, or not known
Error: unable to SSH to the server in batch mode.
Please fix your SSH client config and try again.
Thanks for the fix!
Sure thing. I appreciate your bug report.
Hi!
First of all, thank you for all the great work!
I am trying to follow the steps and I am encountering this:
Might be some bug in the script?