use force option when doing a docker rm of the container image

XMLWordPrintable

      a SAGA user reported jobs running with docker containers to be failing

      python_panx27_import_kb.err.000 has this:
      #########################[Container] Launching user task #########################
      Error: No such container: python_panx27_import_kb-47fa23d6-dfaf-4dbc-bb00-9b89fd0715b4
      2021-08-25 11:33:05: User task failed with exitcode 1
      2021-08-25 11:33:05: /tmp/pegasus.3JCQAI89h cleaned up
      PegasusLite: exitcode 1

      this error is when the pegasus lite script attempts to rm the container from the local node registry

      docker run --user root -v $PWD:/scratch -w=/scratch --entrypoint /bin/sh --rm --link db:mongo -v /scratch/dockermount/m36_test/LDC2020E27_AIDA_Phase_2_Practice_Topics_Reference_Knowledge_Base_V1.1/data:/data --name $cont_name $cont_image -c "set -e ;export root_path=\$PATH ;if ! grep -q -E "^$cont_group:" /etc/group ; then groupadd --gid $cont_groupid $cont_group ;fi; if ! id $cont_user 2>/dev/null >/dev/null; then useradd --uid $cont_userid --gid $cont_groupid $cont_user; fi; su $cont_user -c \"./python_panx27_import_kb-cont.sh \""
      job_ec=$(($job_ec + $?))

      docker rm $cont_name 1>&2
      job_ec=$(($job_ec + $?))

            Assignee:
            Karan Vahi
            Reporter:
            Karan Vahi
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: