Yes. My suggestion is to write the error message here.
fatal: [10.52.2.13]: FAILED! => {"changed":true, "cmd": "bash script.sh", "delta": "0.:00:00.003923", "end":"2022-06-01 09:24:57.151834", "msg":"non-zero return code", "rc":127, "start": "2022-06-01 09:24:57:147911", "stderr": script.sh: line 1: conda: command not found\nscript.sh: line 2: python: command not found", "stderr_lines": ["script.sh: line 1: conda: command not found", "script.sh: line2: python: command not found"], "stdout": "", "stdout_lines": []} This when I put "conda activate <env>" inside a bash scipt and tried to run it. I am facing similar error when I pass into shell: conda activate <env> or shell: source script.sh
verify you have Python in your EC2 instance. the error message is super clear
Обсуждают сегодня