Skip to content

Explain the connection between packages, containers and Galaxy#80

Open
wm75 wants to merge 1 commit intomainfrom
wm75-container-intro-writeup
Open

Explain the connection between packages, containers and Galaxy#80
wm75 wants to merge 1 commit intomainfrom
wm75-container-intro-writeup

Conversation

@wm75
Copy link
Copy Markdown
Member

@wm75 wm75 commented Mar 17, 2026

Polished notes from introduction given by Björn.

Polished notes from introduction given by Björn

**conda-forge**

On the conda-forge side, there is a dedicated github repo for development of each individual package recipe.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
On the conda-forge side, there is a dedicated github repo for development of each individual package recipe.
On the conda-forge side, there is a dedicated github repository for development of each individual package recipe.


**bioconda**

The bioconda community has organized all of their channel's package recipes as folders within a single github repo at https://github.com/bioconda/bioconda-recipes.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The bioconda community has organized all of their channel's package recipes as folders within a single github repo at https://github.com/bioconda/bioconda-recipes.
The bioconda community has organized all of their channel's package recipes as folders within a single github repository at https://github.com/bioconda/bioconda-recipes.


overview provided by @bgruening

for an overview picture, see: https://github.com/BioContainers/singularity-build-bot/blob/master/README.md#broader-context
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
for an overview picture, see: https://github.com/BioContainers/singularity-build-bot/blob/master/README.md#broader-context
For an overview picture, see: https://github.com/BioContainers/singularity-build-bot/blob/master/README.md#broader-context

@@ -0,0 +1,140 @@
# Conda, (Bio)Containers and Galaxy

overview provided by @bgruening
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
overview provided by @bgruening
Overview provided by @bgruening

- Can build containers (docker or singularity ones) from any kind of software package, but only the conda packaging format is relevant for this topic.
- involucro is configurable through lua extension scripts

2. conda
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. conda
2. Conda


Once a pull request against any conda-forge package's development repo gets accepted, a new version of that package gets built and deposited under the conda-forge channel at anaconda.org. No further building of artifacts happens on the conda-forge side.

**bioconda**
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**bioconda**
**Bioconda**


The bioconda contribution workflow is described at https://bioconda.github.io/.

When a pull request against the bioconda-recipes repo gets merged, packages touched by the PR get built and deposited under the bioconda channel at anaconda.org.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When a pull request against the bioconda-recipes repo gets merged, packages touched by the PR get built and deposited under the bioconda channel at anaconda.org.
When a pull request against the bioconda-recipes repository gets merged, packages touched by the PR get built and deposited under the bioconda channel at anaconda.org.


for an overview picture, see: https://github.com/BioContainers/singularity-build-bot/blob/master/README.md#broader-context

but lets start from the beginning.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
but lets start from the beginning.
but let's start from the beginning.


2. conda

A programming language and OS-agnostic package management sytem.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A programming language and OS-agnostic package management sytem.
A programming language and OS-agnostic package management system.

- checks against quay.io to see if a mulled container image with this hash already exists
- if not, creates pull requests against the biocontainers/multi-package-containers under the bot account @dockerhub-toolshed.

These PRs do not touch the combinations/hash.tsv file like manually created PRs, but instead create a dedicated file per container, like e.g. [here](https://github.com/BioContainers/multi-package-containers/pull/3899/changes), but when they get merged the cause docker and singularity image uploads like for manually created PRs.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but when they get merged the cause docker and singularity image uploads like for manually created PRs.

the statement is not so clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants