The requirement to use “./“ is a known issue and scheduled to be fixed in 8.5.6, to be released … today?
In addition to Todd’s suggestion, I would suggest also doing “ls /“ and “hostname” inside foo.sh to see if you get the host filesystem / name or the container.
Well, that’s embarrassing! That’s right, so fixed the typo. Now, if I have executable = ./foo.sh, it runs but appears to run outside of docker container (e.g. my script foo.py failed in such a way that it would not if inside the container). I tried “executable=foo.sh” without “./“ and get the same error as before.
Getting closer though!
Hi Mike,I see you're transferring foo.py twice, but calling ./foo.sh?Is that a typo or is foo.sh embedded in the docker image?Cheers, Iain________________________________________From: HTCondor-users [htcondor-users-bounces@xxxxxxxxxxx] on behalf of Michael Fienen [mike@xxxxxxxxxxx]Sent: 02 August 2016 14:10To: HTCondor-Users Mail ListSubject: [HTCondor-users] Docker cmdnotfoundHello HTCondorians!I’m trying a trivial Docker universe job and it’s *almost* working.I’m quite certain that HTCondor was able to make a running container (it took forever the first time, presumably because pulling from docker hub, and subsequent runs are faster but now hanging up).Here’s my simple submit file:universe=dockerdocker_image=mnfienen/centos6_py35notification=neverexecutable=./foo.shshould_transfer_files=YESoutput=out_$(Process).outerror=err_$(Process).errlog = log_$(Process).logtransfer_input_files = foo.py, foo.pyqueueAnd here’s what I get in the log before it goes to held status:007 (234.000.000) 08/02 07:00:07 Shadow exception!Error from slot1_1@xxxxxxx<mailto:slot1_1@xxxxxxx>.xxx.gov<http://xxx.gov>: Error running docker job: cmdnotfound0 - Run Bytes Sent By Job320 - Run Bytes Received By Job...012 (234.000.000) 08/02 07:00:07 Job was held.Error from slot1_1@xxxxxxx<mailto:slot1_1@xxxxxxx>.xxx.gov<http://xxx.gov>: Error running docker job: cmdnotfoundCode 6 Subcode 0I’ve tried a couple things for the executable argument (foo.sh is simply running foo.py which works in the container locally). I tried "executable=foo.sh”, “executable=./foo.sh”, and before that also tried “executable=python foo.py”I’m clearly doing something wrong.Thanks for any help!Cheers,MIke FienenUSGS Wisconsin Water Science Center_______________________________________________HTCondor-users mailing listTo unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with asubject: UnsubscribeYou can also unsubscribe by visitinghttps://lists.cs.wisc.edu/mailman/listinfo/htcondor-usersThe archives can be found at:https://lists.cs.wisc.edu/archive/htcondor-users/
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx
You can also unsubscribe by visitinghttps://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at: