Todd, Brian, I found out that centos-provided docker rpms don't work with condor: docker socket is not writable by a dedicated group. So I replaced them with the upstream docker-ce. Now on some hosts "hasdocker" is true and StarterLog contains > 10/29/19 15:02:28 (pid:1354) DockerProc::Version() found version 'Docker version 19.03.4, build 9013bf583a' > 10/29/19 15:02:28 (pid:1354) '/usr/bin/singularity --version' did not exit successfully (code 0); the first line of output was ''. These are "CentOS Linux release 7.7.1908 (Core)" w/ docker-ce-19.03.4-3.el7.x86_64 and a mix of condor-8.8.5-1.el7.x86_64 and condor-8.6.13-1.el7.x86_64 (stil upgrading). On some other hosts "hasdocker" is false and StarterLog contains > 10/31/19 13:08:39 (pid:1798) '/usr/bin/docker info' did not exit successfully (code 256); the first line of output was 'WARNING: Error loading config file: /root/.docker/config.json: stat /root/.docker/config.json: permission denied'. > 10/31/19 13:08:39 (pid:1798) '/usr/bin/singularity --version' did not exit successfully (code 32708); the first line of output was ''. Those are all condor-8.8.5-1.el7.x86_64, centos and docker-ce versions as above. None of them have /root/.docker/config.json, the warning does not pop up when I run `docker info` from command line (as either root or condor) and its exit code is 0. Any idea what's going wrong? -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
Attachment:
signature.asc
Description: OpenPGP digital signature