Leo Chen
Compared to emulated amd64 images, the native arm64 builds seem significantly faster. It is a useful tool for researchers on Apple Silicon who need reliable container solutions.
Questions about aarchbio
What is aarchbio?
aarchbio provides native arm64 (aarch64) rebuilds of BioContainers for bioinformatics workflows, publishing over 500 tool containers including samtools, bwa, kraken2, gatk4, and salmon hosted on quay.io/aarchbio for Apple Silicon Macs and AWS Graviton instances.
What is the scope of aarchbio's rebuild efforts?
The project rebuilds existing BioContainers and bioconda packages as native linux-aarch64 images so that pipelines built on nf-core and Nextflow can run without relying on QEMU emulation, with source code published on GitHub under the Apache 2.0 license.
How does aarchbio ensure container security and provenance?
Every image is cosign keyless-signed in CI and logged to the Sigstore transparency log, ensuring provenance and traceability for the signed, public containers distributed without requiring an account.
What is the specific build process aarchbio uses?
The project deliberately avoids compiling from source to maintain the verifiable-build trust model, instead rebuilding bioinformatics tool containers using the same native recipe as the original BioContainers.
How does aarchbio handle architecture-neutral packages?
Multi-arch manifests are published for Python/Java tools, allowing Docker to automatically pick the native architecture on any host, whether Mac or Graviton, without needing emulation.
What gap does aarchbio identify in the bioinformatics ecosystem?
The audit found that while about a third of bioconda packages are noarch and another third ship native linux-aarch64 builds, every container pulled by five popular nf-core pipelines remains amd64-only.
Which upstream projects does aarchbio depend on?
aarchbio stands on the shoulders of bioconda, BioContainers, nf-core, and Seqera/Wave, relying on an enormous, mostly-volunteer community to build its native arm64 container library.
What layers of the software stack does aarchbio intentionally exclude?
The project focuses on rebuilding the BioContainers / bioconda layer specifically, leaving distro base images like ubuntu and framework packages like tensorflow to other layers that already handle arm64.
How does aarchbio handle tools that cannot be rebuilt?
When a tool cannot be built, the cause usually lives in the distro base or framework layers, which are surfaced in GAPS.md and fixed upstream where they belong.
What is the organizational structure of aarchbio?
The project is an unofficial community effort by Playground Logic, not affiliated with or endorsed by BioContainers, bioconda, nf-core, Seqera, or AWS.
What common theme appears in user feedback?
Some reviewers complain that the containers haven't caught up to the bioconda packages already working on arm64, creating a gap between package availability and container publishing.
What is the primary motivation behind aarchbio's existence?
The website states that aarchbio fills a gap where arm64 simply hasn't finished catching up, noting that machines researchers use are increasingly arm64 but ~10,000 BioContainers images are still essentially all linux/amd64.
What is the official website of aarchbio?
The official website of aarchbio is aarch.bio.
How is aarchbio rated on Trustburn?
On Trustburn, aarchbio has a rating of 3.8 out of 5 based on 5 reviews.
AI-generated from reviews on this page. Verify anything important with the company directly.
Diana Kowalski
While the technical approach of rebuilding BioContainers for arm64 is sound, the pricing model for enterprise features is not entirely clear from the provided information. The service is described as public and signed, which is good, but there is no explicit mention of cost structures for larger teams or specific usage tiers. The gap in coverage for certain mulled images is also a consideration. For someone considering this company, it is worth verifying if the current free offering meets all long-term needs or if hidden costs exist for extended support. The audit mentions performance gains, but the financial transparency regarding extended use cases is lacking compared to the technical details.
Jonas Lindström
aarchbio addresses a specific need in the bioinformatics community by rebuilding containers for Apple Silicon and AWS Graviton. The use of keyless signing via Sigstore and transparency logs allows users to verify provenance easily. This trust model, combined with the daily automated rebuilds, ensures that the tools remain secure and up-to-date with the latest bioconda releases.
Mara Velez
The approach to rebuilding BioContainers natively for arm64 architectures is impressive. By leveraging the existing bioconda packages and focusing on the container gap, they offer a streamlined solution. The daily reconciler ensures tools remain current without manual intervention.
Elias Thorne
It is wonderful to see aarchbio providing native arm64 BioContainers for Apple Silicon and AWS Graviton. The fact that these are public and signed adds great trust for researchers using these platforms.
News
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
Widgets
Get the widget for your site →About aarchbio
aarchbio provides native arm64 (aarch64) rebuilds of BioContainers for bioinformatics workflows. It publishes over 500 bioinformatics tool containers, including tools such as samtools, bwa, kraken2, gatk4, and salmon, hosted on quay.io/aarchbio for use with Apple Silicon Macs and AWS Graviton instances. The project focuses on rebuilding existing BioContainers and bioconda packages as native linux-aarch64 images so that pipelines, including those built on nf-core and Nextflow, can run without relying on QEMU emulation. The containers are signed, public, and distributed without requiring an account, with the source code published on GitHub under the Apache 2.0 license.
- Website
- aarch.bio
- Categories
- Computer software, Research, Biotechnology