Re: [HTCondor-users] Docker cannot inspect exited container

["Schock, Justus" <Justus.Schock@xxxxxxxxxxxxxxxxxx>]

Hi, 

no that isnât intentional. Is there a configuration variable that could be causing this?

Other than that - why canât condor kill the job? Shouldnât it be possible to do so anyways?

-Justus

On 6. Dec 2021, at 17:43, Greg Thain <gthain@xxxxxxxxxxx> wrote:

ï

On 12/6/21 8:32 AM, Schock, Justus wrote:

Hi,

When running jobs with the docker universe, I always get the following error message:

12/06/21 15:26:24 (pid:3819363) Create_Process succeeded, pid=3819365

12/06/21 15:26:24 (pid:3819363) Suspending all jobs.

12/06/21 15:26:24 (pid:3819363) DockerProc::Suspend() container 'HTCJob50126_0_slot1_1_PID3819363'

Hi:

It looks like condor is trying to suspect the docker job immediately after starting it.  Is this intentional in your pool -- suspend means that the job is still using the slot, but has effectively been sent SIGSTOP, so that it isn't using any cpu.

-greg

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/