[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Major upgrade from Singularity to Apptainer coming



Hi Stuart,

On 10/6/22 17:52, Anderson, Stuart B. wrote:
On Oct 6, 2022, at 10:43 AM, Greg Thain via HTCondor-users <htcondor-users@xxxxxxxxxxx> wrote:

On 10/5/2022 7:10 PM, Anderson, Stuart B. wrote:
Now that Apptainer 1.1.0 [1] is readily available from EPEL 8 is there
any need to couple this transition from singularity to a particular
release of Condor?

Stuart

As long as Apptainer is installed with the singularity compatibility, there are no HTCondor updates needed.
Greg,
	How do I silence the following several pages of DEPRECATED USAGE messages for my users? Note, I have already gotten rid of /etc/singularity on the example AP.


[stuart.anderson@condor-f3 ~]$ condor_version
$CondorVersion: 9.12.0 2022-10-05 BuildID: 608474 PackageID: 9.12.0-1 $
$CondorPlatform: x86_64_AlmaLinux8 $

[stuart.anderson@condor-f3 ~]$ condor_run -a accounting_group=cit.test -a request_disk=10m "/bin/hostname -f && condor_version"
acas0714.usatlas.bnl.gov
$CondorVersion: 9.0.16 Aug 16 2022 PackageID: 9.0.16-1.1 $
$CondorPlatform: X86_64-CentOS_7.9 $
WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_HAS_CVMFS_IGWN_PRIVATE_DATA as environment variable will not be supported in the future, use APPTAINERENV_HAS_CVMFS_IGWN_PRIVATE_DATA instead
WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV_HAS_FILE_lib64_libglib_2_0_so_0 as environment variable will not be supported in the future, use APPTAINERENV_HAS_FILE_lib64_libglib_2_0_so_0 instead
WARNING: DEPRECATED USAGE: Forwarding SINGULARITYENV__CONDOR_SCRATCH_DIR_OUTSIDE_CONTAINER as environment variable will not be supported in the future, use APPTAINERENV__CONDOR_SCRATCH_DIR_OUTSIDE_CONTAINER instead
...

Those warnings are thrown for each 'SINGULARITYENV_' var that does not have a corresponding 'APPTAINERENV_' var and this was addressed in HTCondor 9.0.17 and 9.10.0 here: https://opensciencegrid.atlassian.net/browse/HTCONDOR-1137. It turned out that the factory config needed to be updated for 9.0.17 but that's done so new pilots should not have this problem. Let us know if you continue to see it on new pilots!

- Brian