opensource/galaxy
3
0
Fork 0
mirror of https://github.com/galaxyproject/galaxy.git synced 2026-10-29 17:42:12 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #16280 from mvdbeek/container_resolver_followup

Browse Source 
Improve container resolver documentation
This commit is contained in:
Marius van den Beek
2023-06-22 11:30:22 +02:00
committed by GitHub
parent a381580349 dd653f71d2
commit fb11e30bf8
3 changed files with 30 additions and 49 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/admin/container_resolvers.rst
+5 -7
View File
@@ -166,17 +166,15 @@ an entry in the docker image cache (on the local node) whereas for
singularity an image file is created in the specified ``cache_directory``.
On distributed systems ``cache_directory`` needs to be accessible on all
compute nodes.
For singularity admins should also take care of the ``APPTAINER_CACHEDIR``
For singularity, admins should also take care of the ``APPTAINER_CACHEDIR``
directory.
.. note::
Using a cached docker resolver has no additional value on distributed compute
systems since the cache is only available locally.
Therefore an additional ``docker inspect ... ; [ $? -ne 0 ] && docker pull ...``
command is used in each job script. Thereby a container will be cached
after the tool run even if no cached container resolver was used.
Clearly admins need to take care of docker caches of the main and compute nodes.
An additional ``docker inspect ... ; [ $? -ne 0 ] && docker pull ...``
command is used in each job script to ensure that images are available on a compute node.
Thereby a container will be cached after the tool run even if no cached container resolver was used.
Admins need to take care of docker caches of the main and compute nodes.
For distributed compute systems, built-in techniques of docker may be useful:
https://docs.docker.com/registry/recipes/mirror/.