GenieACS

Production-ready Docker image for GenieACS, an open-source TR-069 (CWMP) Auto Configuration Server.

  • Network Services
  • Tools & Utilities
Production-ready Docker image for GenieACS, an open-source TR-069 (CWMP) Auto Configuration Server. Manage and provision CPE devices (routers, ONTs, gateways) via TR-069 with a built-in web UI, REST API, and firmware file server. Multi-arch (amd64/arm64), non-root runtime, integrated log rotation. Runs four services in one container managed by supervisord: CWMP (device communication), NBI (REST API), FS (file server), and UI (web dashboard). Requires a MongoDB instance.

Platform availability

Available on 1 of 9 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)

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.

63/100 Good

Maintained
98last commit 5 days ago
Popular
43135 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
403 GB minimum RAM, runs on ARM

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

GitHub stars
135
Open issues
0
Last commit
2026-10-08
Latest release
genieacs-0.6.0
License
GPL-3.0
Activity
rising

Checked 5 days ago - source: GitHub (GeiserX/genieacs-container)

Resources & Compatibility

Minimum requirements: 3 GB RAM, 2 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Install and start MongoDB Add the MongoDB 8.0 package list, install mongodb-org, and enable/start it with systemctl enable --now mongod (systemctl is the Linux service manager). GenieACS needs MongoDB to store its settings, and enabling it keeps the database running after a reboot. source
  • Install Redis too Install redis-server from the Ubuntu repository, because GenieACS uses Redis for fast temporary storage. If Redis is missing, parts of the app may fail or run poorly. source
  • Install GenieACS and set up GUI DB Install GenieACS with Yarn (a JavaScript package manager) into /opt, create the /opt/genieacs shortcut, and if you use the Ruby/Rails GUI run bundle and rails db:migrate RAILS_ENV=development. This puts the app where the docs expect it and creates the database tables the web interface needs. source

Fetched 15 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need a separate MongoDB for the GenieACS Docker deployment?

The image runs the GenieACS services, and MongoDB runs beside it. Docker Compose can run both on one host, and Helm can use a bundled evaluation MongoDB or your own MongoDB supplied through a Kubernetes Secret.

Which ports are used for the web console and initial CPE communication?

The web console uses port 3000, and CPE devices inform the ACS on port 7547. On Kubernetes, you can port-forward the genieacs-http service to port 3000 to reach the console.

What should I change before exposing the web console?

Change GENIEACS_UI_JWT_SECRET from changeme in the compose file before you expose the console.

Can I test GenieACS before connecting real routers or ONTs?

Yes, a simulated CPE is available with the testing profile. This lets you try the console before any hardware informs.

Answers sourced from github.com

Community

Collected 14 days ago - public community threads