Project

General

Profile

Actions

Bug #5794

closed

Docker run shows up everytime in the beginning of a job and the task exists 1 but the job still continues.

Added by Bryan Cosca about 9 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-

Description

from qr1hi-8i9sb-9wytp6ji25uxiwt

2015-04-22_23:58:59 salloc: Granted job allocation 274
2015-04-22_23:59:01 qr1hi-8i9sb-9wytp6ji25uxiwt 11685 running from /usr/local/arvados/src/sdk/cli/bin/crunch-job with arvados-cli Gem version(s) 0.1.20150205181653, 0.1.20150128223752, 0.1.20150121183928, 0.1.20141209151444, 0.1.20141014201516, 0.1.20140919104705, 0.1.20140905165259, 0.1.20140827170424, 0.1.20140825141611, 0.1.20140812162850, 0.1.20140708213257, 0.1.20140707162447, 0.1.20140630151639, 0.1.20140513131358, 0.1.20140513101345, 0.1.20140414145041
2015-04-22_23:59:01 qr1hi-8i9sb-9wytp6ji25uxiwt 11685 check slurm allocation
2015-04-22_23:59:01 qr1hi-8i9sb-9wytp6ji25uxiwt 11685 node compute19 - 1 slots2015-04-22_23:59:01 qr1hi-8i9sb-9wytp6ji25uxiwt 11685 start
2015-04-22_23:59:02 qr1hi-8i9sb-9wytp6ji25uxiwt 11685 Clean work dirs
2015-04-22_23:59:02 starting: ['srun','--nodelist=compute19','-D','/tmp','bash','-ec','mount -t fuse,fuse.keep | awk \'($3 ~ /\\ykeep\\y/){print $3}\' | xargs -r -n 1 fusermount -u -z; sleep 1; rm -rf $JOB_WORK $CRUNCH_INSTALL $CRUNCH_TMP/task $CRUNCH_TMP/src* $CRUNCH_TMP/*.cid']
2015-04-22_23:59:03 qr1hi-8i9sb-9wytp6ji25uxiwt 11685 Cleanup command exited 0
2015-04-22_23:59:03 starting: ['srun','--nodelist=compute19','/bin/sh','-ec',' if ! /usr/bin/docker.io images -q --no-trunc --all | grep -qxF d33416e64af4370471ed15d19211e84991a8e158626199f4e4747e4310144b83; then arv-get 17b65db74aae73465b5e286d1cdb0e23\\+798\\/d33416e64af4370471ed15d19211e84991a8e158626199f4e4747e4310144b83\\.tar | /usr/bin/docker.io load fi ']
2015-04-22_23:59:34 starting: ['srun','--nodelist=compute19','/bin/sh','-ec','/usr/bin/docker.io run --help | grep -qe --memory-swap=']
2015-04-22_23:59:34
2015-04-22_23:59:34 Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
2015-04-22_23:59:34
2015-04-22_23:59:34 Run a command in a new container
2015-04-22_23:59:34
2015-04-22_23:59:34 -a, --attach=[] Attach to STDIN, STDOUT or STDERR.
2015-04-22_23:59:34 --add-host=[] Add a custom host-to-IP mapping (host:ip)
2015-04-22_23:59:34 -c, --cpu-shares=0 CPU shares (relative weight)
2015-04-22_23:59:34 --cap-add=[] Add Linux capabilities
2015-04-22_23:59:34 --cap-drop=[] Drop Linux capabilities
2015-04-22_23:59:34 --cidfile="" Write the container ID to the file
2015-04-22_23:59:34 --cpuset="" CPUs in which to allow execution (0-3, 0,1)
2015-04-22_23:59:34 -d, --detach=false Detached mode: run the container in the background and print the new container ID
2015-04-22_23:59:34 --device=[] Add a host device to the container (e.g. --device=/dev/sdc:/dev/xvdc)
2015-04-22_23:59:34 --dns=[] Set custom DNS servers
2015-04-22_23:59:34 --dns-search=[] Set custom DNS search domains
2015-04-22_23:59:34 -e, --env=[] Set environment variables
2015-04-22_23:59:34 --entrypoint="" Overwrite the default ENTRYPOINT of the image
2015-04-22_23:59:34 --env-file=[] Read in a line delimited file of environment variables
2015-04-22_23:59:34 --expose=[] Expose a port from the container without publishing it to your host
2015-04-22_23:59:34 -h, --hostname="" Container host name
2015-04-22_23:59:34 -i, --interactive=false Keep STDIN open even if not attached
2015-04-22_23:59:34 --link=[] Add link to another container in the form of name:alias
2015-04-22_23:59:34 --lxc-conf=[] (lxc exec-driver only) Add custom lxc options --lxc-conf="lxc.cgroup.cpuset.cpus = 0,1"
2015-04-22_23:59:34 -m, --memory="" Memory limit (format: , where unit = b, k, m or g)
2015-04-22_23:59:34 --name="" Assign a name to the container
2015-04-22_23:59:34 --net="bridge" Set the Network mode for the container
2015-04-22_23:59:34 'bridge': creates a new network stack for the container on the docker bridge
2015-04-22_23:59:34 'none': no networking for this container
2015-04-22_23:59:34 'container:': reuses another container network stack
2015-04-22_23:59:34 'host': use the host network stack inside the container. Note: the host mode gives the container full access to local system services such as D-bus and is therefore considered insecure.
2015-04-22_23:59:34 -P, --publish-all=false Publish all exposed ports to the host interfaces
2015-04-22_23:59:34 -p, --publish=[] Publish a container's port to the host
2015-04-22_23:59:34 format: ip:hostPort:containerPort | ip::containerPort | hostPort:containerPort | containerPort
2015-04-22_23:59:34 (use 'docker port' to see the actual mapping)
2015-04-22_23:59:34 --privileged=false Give extended privileges to this container
2015-04-22_23:59:34 --restart="" Restart policy to apply when a container exits (no, on-failure[:max-retry], always)
2015-04-22_23:59:34 --rm=false Automatically remove the container when it exits (incompatible with -d)
2015-04-22_23:59:34 --security-opt=[] Security Options
2015-04-22_23:59:34 --sig-proxy=true Proxy received signals to the process (even in non-TTY mode). SIGCHLD, SIGSTOP, and SIGKILL are not proxied.
2015-04-22_23:59:34 -t, --tty=false Allocate a pseudo-TTY
2015-04-22_23:59:34 -u, --user="" Username or UID
2015-04-22_23:59:34 -v, --volume=[] Bind mount a volume (e.g., from the host: -v /host:/container, from Docker: -v /container)
2015-04-22_23:59:34 --volumes-from=[] Mount volumes from the specified container(s)
2015-04-22_23:59:34 -w, --workdir="" Working directory inside the container
2015-04-22_23:59:34 srun: error: compute19: task 0: Exited with exit code 1

Actions #1

Updated by Brett Smith over 8 years ago

Note that this output doesn't show up in the final job log. You have to watch the live stderr logs.

I note that this version of Docker doesn't have the switch we were searching for (--memory-swap). It's possible that it didn't have --help either, resulting in this message on stderr. It's possible that we've already fixed this by upgrading Docker.

Actions #2

Updated by Tom Clegg over 4 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF