Thanks, Jamie. This is super helpful.
> The docker_pull_policy submit command influences how a Docker container image is retrieved on the EP. It is consulted both when the job universe is âdocker' and when the job universe is âsingularity' using a Docker repository path for the container_image.
So, if I understand this correctly, I should switch this back to using the "docker_pull_policy" with the container universe in my HTCondor submit description files and I should still be able to have this work, correct?
> Docker is the only supported containerization system under the container universe that includes an image cache, so we didnât add a separate 'container_pull_policyâ submit command.
This last sentence surprised me. Does that mean that if I'm using a .sif Apptainer container
```
universe = container
container_image = oras://ghcr.io/uw-madison-dsi/pixi-docker-chtc:hello-pytorch-noble-cuda-12.9-apptainer
```
that container image isn't cached at all, and so is pulled from GitHub Container Registry every time?
Best,
Matthew
From: Jaime Frey <jfrey@xxxxxxxxxxx>
Sent: Monday, June 16, 2025 15:19 To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx> Cc: Matthew Feickert <matthew.feickert@xxxxxxxx> Subject: Re: [HTCondor-users] condor_submit pull policy for container universe vs. docker universe The docker_pull_policy submit command influences how a Docker container image is retrieved on the EP. It is consulted both when the job universe is âdocker' and when the job universe is âsingularity' using a Docker
repository path for the container_image.
Docker is the only supported containerization system under the container universe that includes an image cache, so we didnât add a separate 'container_pull_policyâ submit command.
- Jaime
|