Pipe Bomb Docker

Docker Compose setup for running Pipe Bomb. Includes the API server, frontend, and an Nginx reverse proxy that ties them together under a single port.

Getting Started

Docker Compose (recommended)

Suitable for Linux servers or any platform with Docker Compose support.

Download docker-compose.yml:

curl -o docker-compose.yml https://raw.githubusercontent.com/Pipe-Bomb/docker/master/docker-compose.yml

And run it!

docker compose up -d

That's it. Pipe Bomb will be available by default on port 9193. You can configure Pipe Bomb under Docker Compose using the following environment variables:

Single container

Suitable for Unraid, Portainer, and platforms without Docker Compose support.

docker run -d \
  --name pipe-bomb \
  -p 9193:80 \
  -v /path/to/data:/data \
  -v /path/to/resources:/resources \
  -v /path/to/cache:/audio-cache \
  -v /path/to/plugin-cache:/plugin-cache \
  -v /path/to/plugins:/plugins \
  -v /path/to/temp:/temp \
  -v /path/to/music:/music:ro \
  ghcr.io/pipe-bomb/pipe-bomb:latest

Data Storage

Each volume path can be configured independently regardless of how you install your Pipe Bomb. Here's what each one stores:

Local Music Library

To expose a local music directory to Pipe Bomb, set MUSIC_PATH in your .env to the path of your music folder. The Local Library plugin will then be able to scan /music inside the container.

Credits & Contributing

Pipe Bomb is conceptualised and developed by eyezah, but contributions are welcome!