使用 SSH 连接和启动脚本运行 bash 脚本时出现不同的行为

Question

I am trying to run a script which is running on GCP startup-script, my startup script looks like below:

#!/bin/bash
ulimit -n 100000
source ~/miniconda3/etc/profile.d/conda.sh
conda activate base
set -e
/root/miniconda3/bin/python3.8 /root/spider/src/rotate_ip.py & /root/miniconda3/bin/python3.8 /root/spider/src/main.py
gcloud compute instances stop scheduled-spider --zone asia-northeast1-b

This script behavior is not same as when I run the program connecting with SSH. It also doesn't show any log error. But when I run the program connecting SSH, it works perfectly. The way I run the program in SSH connection:

/root/miniconda3/bin/python3.8 /root/spider/src/rotate_ip.py & /root/miniconda3/bin/python3.8 /root/spider/src/main.py

My assumption is when I run the program from startup script, it's probably not getting the same environment as in SSH connection. Though I am using the following commands in the startup script to get the same environment but it's not working the same way.

source ~/miniconda3/etc/profile.d/conda.sh
conda activate base

In ssh connection: which bash command gives me /usr/bin/bash . I have also tried this shebang, but no result. Does anyone have any clue what else to try?

I have also tried something like below:

source ~/miniconda3/etc/profile.d/conda.sh
conda activate base
set -e
conda activate base && /root/miniconda3/bin/python3.8 /root/spider/src/rotate_ip.py & /root/miniconda3/bin/python3.8 /root/spider/src/main.py

But no output difference.

Answer 1

Were I doing this, I would use conda run and not muck around with manual activation.

#!/bin/bash
ulimit -n 100000
set -e
conda run -n base python /root/spider/src/rotate_ip.py & 
conda run -n base python /root/spider/src/main.py
gcloud compute instances stop scheduled-spider --zone asia-northeast1-b

If it needs interaction, then you may need additional flags (see conda run --help ).