RetroNAS_inabox

RetroNAS_inabox is an Unraid container that installs a ready-made RetroNAS virtual machine into the VMs tab of your server.

  • Cloud
  • Game Servers
  • Other
  • Tools & Utilities
RetroNAS_inabox is an Unraid container that installs a ready-made RetroNAS virtual machine into the VMs tab of your server. It downloads a virtual disk image, verifies it with a checksum, then creates a VM template and installs the VM for you. It is for Unraid users who want to serve game backups to homebrew-enabled retro consoles without building the RetroNAS image themselves, and works out of the box with default container variables.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

79/100 Good

Maintained
100last commit 18 days ago
Popular
631,438 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
100128 MB minimum RAM
Security check
85no serious findings, tests

Availability: platform listings confirmed today, links checked 11 days ago

GitHub stars
1,438
Open issues
2
Last commit
2026-11-03
License
MIT
Activity
declining

Checked 5 days ago - source: GitHub (danmons/retronas)

Resources & Compatibility

Minimum requirements: 128 MB RAM, 2 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Container variables The 'VM share on server' variable should point to your Unraid VM directory (default /mnt/user/domains), and 'RetroNAS data share' should point to a share for your ROMs (default: retronas) — best to create it empty and move ROMs in later. The VM is attached to this share over virtiofs, so the share does not need to be exported by Unraid. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How is RetroNASinabox installed on an Unraid server?

It is normally run as a container on an Unraid server and downloads the RetroNAS VM directly onto the server. It can also detect whether it is running in a container or as a script.

How does RetroNAS simplify service setup?

RetroNAS uses Ansible to install services. This also helps simplify managing a retro game library.

How does RetroNAS deliver game backups to retro systems?

It is described as a way to stream centralized game backups to retro consoles and network-capable systems.

Why might a Windows client fail to connect to RetroNASinabox?

One user reports that the connection attempt is logged by the system and then quickly terminates. The excerpt asks for other users' experiences and a solution, but it does not state a confirmed fix.

What warnings should be checked before using RetroNAS?

The project information links separate warnings for security and filenames.

Answers sourced from forums.unraid.net, github.com, github.com, www.reddit.com, www.redditmedia.com

Community

Collected 48 days ago - public community threads