From 5601d893a3350a3efca0238d672f059d2404be5c Mon Sep 17 00:00:00 2001 From: pvanheus Date: Fri, 5 Oct 2018 15:24:41 +0200 Subject: [PATCH] Fixes to workding as per nsoranzo --- lib/galaxy/tools/xsd/galaxy.xsd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/galaxy/tools/xsd/galaxy.xsd b/lib/galaxy/tools/xsd/galaxy.xsd index 48a330531ec3..6cca16b5203a 100644 --- a/lib/galaxy/tools/xsd/galaxy.xsd +++ b/lib/galaxy/tools/xsd/galaxy.xsd @@ -314,10 +314,10 @@ resolver. This tag set is contained within the 'requirements' tag set. Galaxy can be configured to run tools within [Docker](https://www.docker.com/) or [Singularity](https://www.sylabs.io/singularity/) containers - this tag allows the tool to suggest possible valid containers for this tool. The contents of the tag should -be a container image identifier appropriate to the particular container runtime being used, e.g. +be a container image identifier appropriate for the particular container runtime being used, e.g. ``quay.io/biocontainers/fastqc:0.11.2--1`` for Docker or ``docker://quay.io/biocontainers/fastqc:0.11.2--1`` (or alternatively ``/opt/containers/fastqc.simg`` if your Galaxy installation will be loading the image from a filesystem path) -for Singularity. The requirements tag can contain multiple ``container`` tags describing suitable container options, in +for Singularity. The ``requirements`` tag can contain multiple ``container`` tags describing suitable container options, in which case the first container that is found by the Galaxy container resolver at runtime will be used. Example: