reset.sh breaking after passing to install.sh during check-minimum-requirements.sh line 3: file not found #1079
Comments
|
Confirmed, thanks for the report @kibble1. Glad someone found |
|
Probably a regression in #1066, lessee here ... |
|
Up for making a PR @kibble1? :) I can get to this in a bit but thought I'd offer ... |
|
Figured I'd better 👍 this issue as I just ran into it myself. 😂 😭 |
chadwhitacre
added a commit
that referenced
this issue
Nov 1, 2021
We need $0 to evaluate as install.sh in order for check-requirements to work.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Version
nightly
Steps to Reproduce
on an existing onpremise setup run ./reset.sh
after the call to install.sh check-minimum-requirements breaks at line 3: with the call to _min_requirements.sh not found.
seems while running in reset.sh and then calling install.sh the working directory changes to onpremise; however if running strictly in install.sh the working directory is onpremise/install
Expected Result
reset.sh and then install.sh should flow correctly
Actual Result
exits with check-minimum-requirements.sh: line 3: /root/onpremise/_min-requirements.sh: No such file or directory
The text was updated successfully, but these errors were encountered: