Re: [HTCondor-users] Docker cmdnotfound

[Iain Bradford Steers <iain.steers@xxxxxxx>]

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:10
To: HTCondor-Users Mail List
Subject: [HTCondor-users] Docker cmdnotfound

Hello 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=docker
docker_image=mnfienen/centos6_py35
notification=never
executable=./foo.sh
should_transfer_files=YES
output=out_$(Process).out
error=err_$(Process).err
log = log_$(Process).log
transfer_input_files = foo.py, foo.py
queue

And 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: cmdnotfound
0  -  Run Bytes Sent By Job
320  -  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: cmdnotfound
Code 6 Subcode 0

I’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 Fienen
USGS Wisconsin Water Science Center