You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.
I would expect that the command in the job description job_specifications.tasks.command of the jobs.yaml leads to the same result as when I use docker run. However, the command option in the job definition seems to overwrite the containers working directory to be $AZ_BATCH_TASK_WORKING_DIR. This is a non-standard procedure and very confusing.
I would expect that shipyard jobs add with the following jobs.yaml produces the same output as docker run busybox pwd.
Instead docker run busybox pwd outputs / and the shipyard job outputs /mnt/batch/tasks/workitems/test/job-1/task-00007/wd. Therefore, if I would want to run code in my own container, I first had to change to the right working directory. I would very much appreciate if you change that behavior - or at least state this very clear in the documentation.
jobs.yaml
job_specifications:
- id: test
tasks:
- docker_image: busybox
command: pwd
The text was updated successfully, but these errors were encountered:
I would expect that the command in the job description
job_specifications.tasks.command
of thejobs.yaml
leads to the same result as when I usedocker run
. However, the command option in the job definition seems to overwrite the containers working directory to be$AZ_BATCH_TASK_WORKING_DIR
. This is a non-standard procedure and very confusing.I would expect that
shipyard jobs add
with the followingjobs.yaml
produces the same output asdocker run busybox pwd
.Instead
docker run busybox pwd
outputs/
and the shipyard job outputs/mnt/batch/tasks/workitems/test/job-1/task-00007/wd
. Therefore, if I would want to run code in my own container, I first had to change to the right working directory. I would very much appreciate if you change that behavior - or at least state this very clear in the documentation.jobs.yaml
The text was updated successfully, but these errors were encountered: