What version of crane are you running, and what are your clutsters+platform
latest from main branch on KIND clusters
Description
If the rsync image predates rclone support , crane accepts the image,
creates the destination PVC, launches the upload pod, and the container fails to start with
exec: "rclone": executable file not found in $PATH.
crane does fail and returns a non-zero exit code like expected , but:
- there is no pre-flight check that
--source-image contains an rclone
binary,
- the top-level error does not name the root cause — it reports only
upload pod failed: pod <ns>/rclone-upload-<pvc> failed, and
- the failure is reached only after the destination PVC is created (a
committed side effect → orphan), and only after the mover pod reaches a
terminal state.
What did you expect to happen?
What actually happened?
Please include any relevant logs or errors
What version of crane are you running, and what are your clutsters+platform
latest from main branch on KIND clusters
Description
If the rsync image predates rclone support , crane accepts the image,
creates the destination PVC, launches the upload pod, and the container fails to start with
exec: "rclone": executable file not found in $PATH.crane does fail and returns a non-zero exit code like expected , but:
--source-imagecontains anrclonebinary,
upload pod failed: pod <ns>/rclone-upload-<pvc> failed, andcommitted side effect → orphan), and only after the mover pod reaches a
terminal state.
What did you expect to happen?
What actually happened?
Please include any relevant logs or errors