Portainer Templates logo

Portainer Templates

Garage Garage

Stack

Object Storage

Garage - the S3-compatible object store the self-hosting community moved to after MinIO archived its open source in 2026: a single static Rust binary, AGPL, actively released, designed for exactly this job.

Configuration

Type
Compose
Platform
linux
Env vars
GARAGE_ADMIN_TOKEN=''GARAGE_RPC_SECRET=''
Source
Repo

Template by deployable-sh·Source

Report issue

Services

garage

Configuration

Ports
39003903
Volumes
/var/lib/garage/meta : garagemeta/var/lib/garage/data : garagedata
Env vars
GARAGE_RPC_SECRET=${GARAGE_RPC_SECRET}GARAGE_ADMIN_TOKEN=${GARAGE_ADMIN_TOKEN}
Restart
unless-stopped
Build
./garage

webui

Configuration

Image
khairul169/garage-webui:1.1.0
Ports
3909
Env vars
API_BASE_URL=http://garage:3903API_ADMIN_KEY=${GARAGE_ADMIN_TOKEN}S3_ENDPOINT_URL=http://garage:3900
Restart
unless-stopped

Image details

Pulls: 1.3M
User: khairul169
Created: Aug 16, 2024
Updated: 1 years ago
Status: active

web

Configuration

Ports
5000:5000
Env vars
PROXY_TARGET=http://webui:3909
Restart
unless-stopped
Build
./proxy

Standalone Install

Select an install method, to see config/commands for deploying Garage

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Garage, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

name: garage

services:
  garage:
    build: ./garage
    restart: unless-stopped
    environment:
      GARAGE_RPC_SECRET: ${GARAGE_RPC_SECRET}
      GARAGE_ADMIN_TOKEN: ${GARAGE_ADMIN_TOKEN}
    ports:
      - "3900"
      - "3903"
    volumes:
      - garagemeta:/var/lib/garage/meta
      - garagedata:/var/lib/garage/data

  webui:
    image: khairul169/garage-webui:1.1.0
    restart: unless-stopped
    environment:
      API_BASE_URL: http://garage:3903
      API_ADMIN_KEY: ${GARAGE_ADMIN_TOKEN}
      S3_ENDPOINT_URL: http://garage:3900
    ports:
      - "3909"
    depends_on:
      - garage

  web:
    build: ./proxy
    restart: unless-stopped
    environment:
      PROXY_TARGET: http://webui:3909
    ports:
      - "5000:5000"
    depends_on:
      - webui

volumes:
  garagemeta:
  garagedata:

Or deploy it directly from the source:

git clone https://github.com/deployable-sh/stacks
cd stacks
docker compose -f garage/compose.yaml up -d

More install options in our documentation.

Container Documentation

webui Documentation

WebUI for Garage Object Storage Service

Serve Garage on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying garage.example.com to http://garage:3900

Add this to your Caddyfile

garage.example.com {
	reverse_proxy http://garage:3900
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5000 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :5000
  • Stop the other service, or pick a different host port. In 5000:5000 only the left number is yours to change, the right one belongs to the app.

Published on a random port

This template exposes 3900 without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:5000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, garage can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5000

Image won't pull

Test the pull directly on the host: docker pull khairul169/garage-webui:1.1.0

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Garage is a Compose stack, a set of containers (3 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 3 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • garage
  • webui runs khairul169/garage-webui:1.1.0, starts after garage
  • web, starts after webui

Ports

A port is the door the app answers on. A mapping like 5000:5000 means it's reachable on port 5000 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 3900, published on a random host port
  • 3903, published on a random host port
  • 3909, published on a random host port
  • 5000:5000

Volumes

A volume is where Garage keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /var/lib/garage/meta kept in the garagemeta volume Docker manages
  • /var/lib/garage/data kept in the garagedata volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Garage takes 6 of them, all with defaults you can leave alone or tweak:

  • GARAGE_RPC_SECRET, pulled from your own environment
  • GARAGE_ADMIN_TOKEN, pulled from your own environment
  • API_BASE_URL, defaults to http://garage:3903
  • API_ADMIN_KEY, pulled from your own environment
  • S3_ENDPOINT_URL, defaults to http://garage:3900
  • PROXY_TARGET, defaults to http://webui:3909

Restart policy

The restart policy here is unless-stopped, so Docker restarts Garage after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like garage) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Garage up. Add the template list to Portainer once, then deploying Garage is a click rather than a wall of config.