From 1270fdd64b9a40c98fd1752497c2eef46f2e3435 Mon Sep 17 00:00:00 2001 From: Charles Coulombe Date: Thu, 12 Jun 2025 13:50:22 -0400 Subject: [PATCH] Update doc/source/admin/special_topics/mulled_containers.rst Co-authored-by: Nicola Soranzo --- doc/source/admin/special_topics/mulled_containers.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/admin/special_topics/mulled_containers.rst b/doc/source/admin/special_topics/mulled_containers.rst index 1c73cea83f4..213b2b08167 100644 --- a/doc/source/admin/special_topics/mulled_containers.rst +++ b/doc/source/admin/special_topics/mulled_containers.rst @@ -24,7 +24,7 @@ requirement field. This approach has shown two limitations that slowed down the adoption by tool developers. First, every tool needs to be annotated with a container name (as shown above) and this container needs -to be created beforehand, usually manually. The second reason is that a Galaxy tool aims to be deployed everywhere, +to be created beforehand, usually manually. The second reason is that Galaxy tools should be deployable everywhere, independent of the underlying system, meaning if Docker is not available Galaxy should use Conda packages. This puts an additional burden on tool developers who need to take care of two dependency resolvers. This setup can cause different tool results depending on the resolver, because both the Conda package and the Docker container are