AKS中CronJob运行PVC内Python脚本失败的解决咨询

问题 #

在AKS中创建CronJob调用PVC内脚本时遇到执行错误，操作流程及问题如下：

1. 创建名为cronjob-scripts的PVC，配置如下：

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    volume.beta.kubernetes.io/mount-options: dir_mode=0777,file_mode=0777,uid=999,gid=999
    volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/azure-file
  name: cronjob-scripts
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 1Gi
  storageClassName: aks-azure-files

2. 将PVC挂载到general-utils Pod，执行命令将Python脚本复制到PVC：

kubectl -n <NAMESPACE> cp cronjob_script.py general-utils:/var/scripts

3. 创建名为testing-cronjob的CronJob，配置如下：

apiVersion: batch/v1
kind: CronJob
metadata:
  name: testing-cronjob
spec:
  schedule: "00 0 * * *"
  concurrencyPolicy: Forbid
  successfulJobsHistoryLimit: 1
  failedJobsHistoryLimit: 1
  startingDeadlineSeconds: 300
  jobTemplate:
    spec:
      template:
        spec:
          imagePullSecrets:
          - name: <SECRET_NAME>
          restartPolicy: OnFailure
          volumes:
          - name: cronjob-scripts
            persistentVolumeClaim:
              claimName: cronjob-scripts
          containers:
          - name: testing-cronjob
            image: <PYTHON_INSTALLED_ALPINE_IMAGE>
            command: ["py /var/scripts/cronjob_script.py"]
            volumeMounts:
            - name: cronjob-scripts
              mountPath: "/var/scripts"
            imagePullPolicy: Always

4. 手动触发CronJob后，Pod报错：

Warning  Failed     13s (x2 over 13s)  kubelet            
Error: failed to create containerd task: failed to create shim task: 
OCI runtime create failed: runc create failed: 
unable to start container process: exec: "py /var/scripts/cronjob_script.py": 
stat py /var/scripts/cronjob_script.py: no such file or directory: unknown

怀疑是PVC挂载时机导致问题，需实现CronJob调用PVC内脚本运行的需求。

解决方案 #

核心问题定位 #

错误并非PVC挂载时机导致，根源是CronJob容器的command配置格式错误：

• Kubernetes的command字段要求以数组形式拆分命令与参数，当前将整个命令作为单个字符串传入，导致容器尝试执行名为py /var/scripts/cronjob_script.py的可执行文件，而非调用py命令并传入脚本路径参数。
• 额外需确认Alpine镜像中Python的命令名称，部分镜像可能使用python或python3而非py。

修正步骤 #

1. 调整CronJob的command配置：
   将原command改为数组格式，同时匹配镜像中正确的Python命令：

   containers:
   - name: testing-cronjob
     image: <PYTHON_INSTALLED_ALPINE_IMAGE>
     # 若镜像中Python命令为python3，替换为["python3", "/var/scripts/cronjob_script.py"]
     command: ["py", "/var/scripts/cronjob_script.py"]
     volumeMounts:
     - name: cronjob-scripts
       mountPath: "/var/scripts"
     imagePullPolicy: Always
   

   若镜像默认ENTRYPOINT指向Python，也可改用args字段：

   containers:
   - name: testing-cronjob
     image: <PYTHON_INSTALLED_ALPINE_IMAGE>
     args: ["/var/scripts/cronjob_script.py"]
     volumeMounts:
     - name: cronjob-scripts
       mountPath: "/var/scripts"
     imagePullPolicy: Always
   

2. 验证PVC内脚本的存在性与权限：
   进入general-utils Pod检查脚本状态：

   kubectl -n <NAMESPACE> exec -it general-utils -- ls -l /var/scripts/cronjob_script.py
   

   若脚本无执行权限，添加权限：

   kubectl -n <NAMESPACE> exec -it general-utils -- chmod +x /var/scripts/cronjob_script.py
   

3. 测试修正后的CronJob：
   删除旧测试Job并重新创建：

   kubectl -n <NAMESPACE> delete job job-of-testing-cronjob
   kubectl -n <NAMESPACE> create job --from=cronjob/testing-cronjob job-of-testing-cronjob
   

   查看Pod日志确认执行结果：

   kubectl -n <NAMESPACE> logs <POD_NAME>
   

额外优化建议 #

• 提前验证镜像中的Python命令：

  docker run --rm -it <PYTHON_INSTALLED_ALPINE_IMAGE> which python
  

• 添加初始化容器检查PVC挂载与脚本存在性：

  initContainers:
  - name: check-script
    image: <PYTHON_INSTALLED_ALPINE_IMAGE>
    command: ["sh", "-c", "test -f /var/scripts/cronjob_script.py || (echo 'Script not found' && exit 1)"]
    volumeMounts:
    - name: cronjob-scripts
      mountPath: "/var/scripts"
  

内容的提问来源于stack exchange，提问作者Wing Choy