From e646c85ef9fa90e2e4931371650dc461598c2d71 Mon Sep 17 00:00:00 2001 From: Charles Coulombe Date: Thu, 12 Jun 2025 11:07:32 -0400 Subject: [PATCH] Update mulled_containers.rst Fixed typo --- 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 332a9806b73..1c73cea83f4 100644 --- a/doc/source/admin/special_topics/mulled_containers.rst +++ b/doc/source/admin/special_topics/mulled_containers.rst @@ -25,7 +25,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, -independet of the underlying system, meaning if Docker is not available Galaxy should use Conda packages. +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 usually not created out of the same recipe and maybe were compiled in a different way, use different sources etc.