Every Biocontainer is deployed and permanent deposited in a public registry Docker Hub or Quay.io. These two registries allows developers and contributors to deploy their software to a public repository without needs to implement a new registry.
What is Docker Hub
Docker Hub is a cloud-based registry service which allows you to link to code repositories, build your images and test them, stores manually pushed images, and links to Docker Cloud so you can deploy images to your hosts. It provides a centralized resource for container image discovery, distribution and change management, user and team collaboration, and workflow automation throughout the development pipeline.
What is Quay.io
Quay.io is a non-profit docker registry which major advance is that support
rkt technologies. In Quay.io each Container is presented with the maximum amount of useful information, including a full tags list, markdown based
description and repository push and pull counts. Repositories can be linked to GitHub, BitBucket, GitLab or custom git repositories, with automatic building of the Dockerfile(s) found on push.
The BioContainers Registry
BioContainers Registry UI provides the interface to and UI to search, tag, and document a BioContainers across all the registries.
The users can search containers by using the search box:
The containers registry allow the users to
sort the containers by any of these properties:
- Container Name: Container Name
- Description: Description Provided by the developer of the container.
- Real Name: The corresponding registry + container name
- Last Modified: Last date where the container has been modified.
- Starred/Start: If the container has been starred in any of the repos.
- Popularity: How many times a container has been pull from a registry.
- Registry Link: the registry Link.
Visualizing a Container Information
The user can click the container name for example, BLAST and see all the documentation related with the container.
Dockerfileprovided by the developer or it will provide the
Yaml(see example) configuration file for the