[HTCondor-users] Can condor still create cgroups when run inside a docker container?

[Boris Sadkhin <bsadkhin.anl@xxxxxxxxx>]

Hi All,

When running a personal condor, I can change âBASE_CGROUP=htcondorâ and jobs launched with condors seem to get the correct cgroup, such as

 

3:memory:/htcondor/condor_var_lib_condor_execute_slot1@localhost

2:cpuacct,cpu:/htcondor/condor_var_lib_condor_execute_slot1@localhost

 

However, when I run htcondor inside of a docker container, with the flag `parent_cgroup = htcondor`

 

I get

 

3:memory:/system.slice/containerd.service/htcondor/d1289ed8e7d08c443bbe29613ed88f80d03b260a5ba6e476a903c0d5eede5a3c

2:cpuacct,cpu:/system.slice/containerd.service/htcondor/d1289ed8e7d08c443bbe29613ed88f80d03b260a5ba6e476a903c0d5eede5a3c

 

Is there a way to let condor manage cgroups when running inside of a docker container?

 

Thanks