Installation
BiomiX 3.0 uses Docker to ensure a stable, reproducible environment across all platforms. The launcher scripts handle everything automatically, no command-line knowledge required.
BiomiX 3.0 requires Docker to be installed on your system. We recommend Docker Engine on Linux/Ubuntu, which is the environment BiomiX 3.0 has been built and tested for. New to Docker? Follow our Docker installation guide.
A local installation without Docker is still possible using the legacy install scripts. See the legacy installation section at the bottom of this page for details.
Download the launcher script for your operating system from the BiomiX GitHub repository.
Place it in a folder of your choice, it will automatically create a biomix_shared
folder nearby for your input data and results.
All launchers are also available in the BiomiX GitHub repository under the launchers/ folder.
The launcher will automatically pull all required Docker modules on first run and open the BiomiX interface in your browser. Select your platform below.
BiomiX_Start.bat, a setup window will appear.http://localhost:3838.Keep the terminal window open while using BiomiX. Closing it will stop the application.
sudo systemctl start dockerBiomiX_Start.sh, and make it executable (first time only):
chmod +x BiomiX_Start.sh
./BiomiX_Start.sh
http://localhost:3838.Keep the terminal open while using BiomiX. Press Ctrl+C to stop it when done.
BiomiX-Launcher-1.0.0.dmg and follow the installation steps.http://localhost:3838.Keep the launcher window open while using BiomiX. Closing it will stop the application.
For advanced users who prefer to pull each module manually. biomix_gui and biomix-base
are always required. Add only the analysis modules relevant to your workflow.
| Module | Pull command | Required |
|---|---|---|
biomix_gui BiomiX graphical interface, Shiny frontend |
docker pull ghcr.io/biomix-consortium/biomix_gui:latest |
Always required |
biomix-base Core R environment used by all analysis modules |
docker pull ghcr.io/biomix-consortium/biomix-base:latest |
Always required |
biomix-transcriptomics Transcriptomics single-omics pipeline |
docker pull ghcr.io/biomix-consortium/biomix-transcriptomics:latest |
Optional |
biomix-methylomics Methylomics single-omics pipeline |
docker pull ghcr.io/biomix-consortium/biomix-methylomics:latest |
Optional |
biomix-metabolomics Metabolomics single-omics pipeline |
docker pull ghcr.io/biomix-consortium/biomix-metabolomics:latest |
Optional |
biomix-mofa MOFA integration method |
docker pull ghcr.io/biomix-consortium/biomix-mofa:latest |
Optional |
biomix-snf SNF integration method |
docker pull ghcr.io/biomix-consortium/biomix-snf:latest |
Optional |
biomix-nemo NEMO integration method |
docker pull ghcr.io/biomix-consortium/biomix-nemo:latest |
Optional |
biomix-diablo DIABLO integration method |
docker pull ghcr.io/biomix-consortium/biomix-diablo:latest |
Optional |
biomix-pramigo Soon PRAMIGO integration method, not yet released |
Coming soon |
Optional |
Once pulled manually, launch the interface with: docker run -p 3838:3838 -v /path/to/data:/shared ghcr.io/biomix-consortium/biomix_gui:latest
PRAMIGO will be released as a separate module shortly after BiomiX 3.0. The launcher will update automatically once it becomes available.
If you run into issues during installation, please open an issue on the consortium's issue tracker or contact us directly at cristian.iperi@univ-brest.fr.
This installation method is no longer actively maintained and may be unstable due to dependency conflicts across platforms. It is preserved for users who cannot use Docker. For all new installations, the Docker-based approach above is strongly recommended.
The local installation creates isolated Python (pyenv) and R (renv) environments and installs all required packages into them, without affecting your system-wide installations. It relies on PyQt5 for the graphical interface.
Download the BiomiX 2.5 release archive from the
BiomiX2.5 GitHub repository,
unzip it, then run the five installation scripts in order from the _INSTALL/ folder.
Run each script in sequence from the _INSTALL/ folder. Each step must complete successfully before moving to the next.
bash _INSTALL/01_BiomiX_install_Python.sh
bash _INSTALL/02_BiomiX_install_R.sh
bash _INSTALL/03_BiomiX_install_R_Packages.sh
bash _INSTALL/04_BiomiX_install_Extension_R_SNF_NEMO.sh
bash _INSTALL/05_BiomiX_install_Extension_R_MintTea.sh
./LaunchApp_BiomiX_Linux.sh
Double-click each .bat file in order from the _INSTALL\ folder. Each step must complete successfully before moving to the next.
.sh script under WSL.LaunchApp_BiomiX_Windows.bat to start BiomiX.Dependency issues are common with the local installation. The most reliable fix is to open an R session inside the BiomiX renv environment, activate renv, and install the missing packages manually.
Activate the BiomiX Python environment and install the missing package:
pip install package-name
Open R inside the BiomiX renv environment and install the missing package:
R
# Inside R:
renv::activate()
renv::install("PackageName")
sudo apt-get install libfontconfig1-dev