Portainer Templates logo

Portainer Templates

RomM RomM

Stack

Entertainment

A beautiful, powerful, self-hosted rom manager.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

romm

Configuration

Image
rommapp/romm:latest
Ports
480:8080
Volumes
/romm/resources : /portainer/Files/AppData/Config/romm/resources/redis-data : /portainer/Files/AppData/Config/romm/redis_data/romm/library : /portainer/roms/library/romm/assets : /portainer/roms/assets/romm/config : /portainer/Files/AppData/Config/romm/config
Env vars
DB_HOST=romm-dbDB_NAME=rommDB_USER=romm-userDB_PASSWD=ROMM_AUTH_SECRET_KEY=IGDB_CLIENT_ID=IGDB_CLIENT_SECRET=MOBYGAMES_API_KEY=STEAMGRIDDB_API_KEY=
Restart
unless-stopped

Image details

Pulls: 10.7M
User: zurdi15
Created: Mar 20, 2024
Updated: 13 days ago
Status: active

romm-db

Configuration

Image
mariadb:latest
Ports
$DB_PORT:3306
Volumes
/var/lib/mysql : /portainer/Files/AppData/Config/romm/maria-db
Restart
unless-stopped

Image details

Pulls: 3.2B
User: stackbrew
Created: Nov 25, 2014
Updated: 2 days ago
Status: active

Standalone Install

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

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 RomM, 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:

services:
  romm:
    image: rommapp/romm:latest
    container_name: romm
    restart: unless-stopped
    environment:
      - DB_HOST=romm-db
      - DB_NAME=romm # Should match MARIADB_DATABASE in mariadb
      - DB_USER=romm-user # Should match MARIADB_USER in mariadb
      - DB_PASSWD= # Should match MARIADB_PASSWORD in mariadb
      - ROMM_AUTH_SECRET_KEY= # Generate a key with `openssl rand -hex 32`
      - IGDB_CLIENT_ID= # Generate an ID and SECRET in IGDB
      - IGDB_CLIENT_SECRET= # https://api-docs.igdb.com/#account-creation
      - MOBYGAMES_API_KEY= # https://www.mobygames.com/info/api/
      - STEAMGRIDDB_API_KEY= # https://github.com/rommapp/romm/wiki/Generate-API-Keys#steamgriddb
    volumes:
      - /portainer/Files/AppData/Config/romm/resources:/romm/resources # Resources fetched from IGDB (covers, screenshots, etc.)
      - /portainer/Files/AppData/Config/romm/redis_data:/redis-data # Cached data for background tasks
      - /portainer/roms/library:/romm/library # Your game library. Check https://github.com/rommapp/romm?tab=readme-ov-file#folder-structure for more details.
      - /portainer/roms/assets:/romm/assets # Uploaded saves, states, etc.
      - /portainer/Files/AppData/Config/romm/config:/romm/config # Path where config.yml is stored
    ports:
      - 480:8080
    depends_on:
      romm-db:
        condition: service_healthy
        restart: true
  romm-db:
    image: mariadb:latest
    container_name: romm-db
    restart: unless-stopped
    env_file:
      - romm.env
    volumes:
      - /portainer/Files/AppData/Config/romm/maria-db:/var/lib/mysql
    healthcheck:
      test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]
      start_period: 30s
      start_interval: 10s
      interval: 10s
      timeout: 5s
      retries: 5
    ports:
      - $DB_PORT:3306

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/romm.yml up -d

More install options in our documentation.

Container Documentation

romm Documentation

A beautiful, powerful, self-hosted rom manager.

romm-db Documentation

MariaDB Server is a high performing open source relational database, forked from MySQL.

Serve RomM 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 romm.example.com to http://romm:8080

Add this to your Caddyfile

romm.example.com {
	reverse_proxy http://romm:8080
}

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:480 failed: port is already allocated", something else on your server is using that port.

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

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:480. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, romm can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 480

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/romm/resources (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull rommapp/romm:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "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.

Required settings are blank

DB_PASSWD, ROMM_AUTH_SECRET_KEY, IGDB_CLIENT_ID, IGDB_CLIENT_SECRET, MOBYGAMES_API_KEY, STEAMGRIDDB_API_KEY have no default value, and romm may crash or misbehave if left empty.

  • Fill them in on the deploy screen before hitting deploy.

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

RomM is a Compose stack, a set of containers (2 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 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • romm runs rommapp/romm:latest, starts after romm-db
  • romm-db runs mariadb:latest

Ports

A port is the door the app answers on. A mapping like 480:8080 means it's reachable on port 480 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:480 in a browser. It opens:

  • 480:8080, likely the web interface

Volumes

A volume is where RomM 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:

  • /romm/resources from /portainer/Files/AppData/Config/romm/resources on the host
  • /redis-data from /portainer/Files/AppData/Config/romm/redis_data on the host
  • /romm/library from /portainer/roms/library on the host
  • /romm/assets from /portainer/roms/assets on the host
  • /romm/config from /portainer/Files/AppData/Config/romm/config on the host
  • /var/lib/mysql from /portainer/Files/AppData/Config/romm/maria-db on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. RomM takes 9 of them, and 6 need a value before it'll start properly:

  • DB_HOST, defaults to romm-db
  • DB_NAME, defaults to romm
  • DB_USER, defaults to romm-user
  • DB_PASSWD, needs a value
  • ROMM_AUTH_SECRET_KEY, needs a value
  • IGDB_CLIENT_ID, needs a value
  • IGDB_CLIENT_SECRET, needs a value
  • MOBYGAMES_API_KEY, needs a value
  • STEAMGRIDDB_API_KEY, needs a value

Restart policy

The restart policy here is unless-stopped, so Docker restarts RomM 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 romm) 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 RomM up. Add the template list to Portainer once, then deploying RomM is a click rather than a wall of config.