opensource/galaxy
3
0
Fork 0
mirror of https://github.com/galaxyproject/galaxy.git synced 2026-09-24 16:30:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix link formats for mulled_containers.rst, minor rewording (#8075)

Browse Source 
Fix link formats for mulled_containers.rst, minor rewording
This commit is contained in:
Björn Grüning
2019-06-01 10:53:51 +02:00
committed by GitHub
parent a763c89180 90f56ebc40
commit 84063a2bfc
1 changed files with 19 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/source/admin/special_topics/mulled_containers.rst
+19 -18
View File
@@ -4,10 +4,10 @@ Containers for Tool Dependencies
Galaxy tools (also called wrappers) are able to use Conda packages
(see more information in our `Galaxy Conda documentation`_) and Docker containers as dependency resolvers.
The IUC_ recommends to use Conda packages as primary dependency resolver, mainly because Docker is not
The IUC_ recommends to use Conda packages as the primary dependency resolver, mainly because Docker is not
available on every (HPC-) system. Conda on the other hand can be installed by Galaxy and maintained
entirely in user-space. Nevertheless, Docker (Containers in general) has some unique features and
there are many use-cases in the Galaxy community which makes containerized systems very appealing.
entirely in user-space. Nevertheless, Docker and containers in general have some unique features and
there are many use-cases in the Galaxy community that make containerized tools very appealing.
Since 2014 Galaxy supports running tools in Docker containers via a special `container annotation`_ inside of the
requirement field.
@@ -41,17 +41,16 @@ is not available already.
Automatic build of Linux containers
-----------------------------------
We utilize [mulled](https://github.com/mulled/mulled) with [involucro](https://github.com/involucro/involucro)
in an automatic way. This is for example used to convert all packages in bioconda_ into Linux Containers
(Docker and rkt at the moment) and made available at the `BioContainers Quay.io account`_.
We utilize mulled_ with involucro_ to automatically convert all packages in Bioconda_ into Linux containers images
(Docker and rkt at the moment) and make them available at the `BioContainers Quay.io account`_.
We have developed small utilities around this technology stack which is currently included in galaxy-lib_.
We have developed small utilities around this technology stack, which is currently included in galaxy-lib_.
Here is a short introduction:
Search for containers
^^^^^^^^^^^^^^^^^^^^^
This will search for containers in the biocontainers organisation.
This will search for containers in the biocontainers organization.
.. code-block:: bash
@@ -72,40 +71,40 @@ The BioConda community is building a container for every package they create wit
Building Docker containers for local Conda packages
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Conda packages can be tested with creating a busybox based container for this particular package in the following way.
Conda packages can be tested with creating a *busybox* based container for this particular package in the following way.
This also demonstrates how you can build a container locally and on-the-fly.
> we modified the samtools package to version 3.0 to make clear we are using a local version
> we modified the ``samtools`` package to version 3.0 to make it clear we are using a local version
1) build your recipe
1) Build your recipe
.. code-block:: bash
$ conda build recipes/samtools
2) index your local builds
2) Index your local builds
.. code-block:: bash
$ conda index /home/bag/miniconda2/conda-bld/linux-64/
3) build a container for your local package
3) Build a container for your local package
.. code-block:: bash
$ mulled-build build-and-test 'samtools=3.0--0' \
--extra-channel file://home/bag/miniconda2/conda-bld/ --test 'samtools --help'
The ``--0`` indicates the build version of the conda package. It is recommended to specify this number otherwise
The ``--0`` indicates the build version of the conda package. It is recommended to specify this number, otherwise
you will override already existing images. For Python Conda packages this extension might look like this ``--py35_1``.
Build, test and push a conda-forge package to biocontainers
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Build, test, and push a conda-forge package to biocontainers
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> You need to have write access to the biocontainers repository
You can build packages from other Conda channels as well, not only from BioConda. ``pandoc`` is available from the
You can build packages from other Conda channels as well, not only from BioConda. ``pandoc`` tool is available from the
conda-forge channel and conda-forge is also enabled by default in Galaxy. To build ``pandoc`` and push it to biocontainrs
you could do something along these lines.
@@ -123,6 +122,8 @@ you could do something along these lines.
.. _IUC: https://galaxyproject.org/iuc/
.. _container annotation: https://github.com/galaxyproject/galaxy/blob/dev/test/functional/tools/catDocker.xml#L4
.. _BioContainers: https://github.com/biocontainers
.. _bioconda: https://github.com/bioconda/bioconda-recipes
.. _mulled: https://github.com/mulled/mulled
.. _involucro: https://github.com/involucro/involucro
.. _Bioconda: https://bioconda.github.io/
.. _BioContainers Quay.io account: https://quay.io/organization/biocontainers
.. _galaxy-lib: https://github.com/galaxyproject/galaxy-lib