Maintenance

Maintenance is an archived, deprecated, unsupported minimal nginx Docker image for self-hosters who need a static maintenance page while their main web server…

  • Monitoring & Logging
  • Other
Maintenance is an archived, deprecated, unsupported minimal nginx Docker image for self-hosters who need a static maintenance page while their main web server is down.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • 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.

15/100 Low

Maintained
0GitHub repository is archived
Popular
144 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

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

GitHub stars
4
Open issues
0
Last commit
2024-12-22
Latest release
1.26.2-r0-ig23
License
GPL-3.0
Activity
stale

Checked 7 days ago - source: GitHub (imagegenius/docker-maintenance)

Resources & Compatibility

Requirements not published yet.

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

First-install notes

  • Install the toolbox first Run sudo bash dist-install.sh so the scripts and config land in the standard /etc/sysconfig or /etc/default spot. Without it, the later setup steps and scheduled jobs won’t find the files they need. source
  • Tell it which drives to check Edit the installed btrfsmaintenance file to set the Btrfs (Linux file system) mount points, which are the folders where your drives are connected, and the maintenance schedule. If this is empty or wrong, the tool may skip your drive or run jobs too often or too rarely. source
  • Enable the scheduled job Run sudo btrfsmaintenance-refresh-cron.sh timer after editing settings to activate the Linux scheduling timer, such as systemd or cron. Without this refresh, the settings exist but the maintenance will not actually start on time. source
  • Deprecated image The image is deprecated and will not receive support or updates; do not use it for new maintenance pages. source
  • Deprecation Upstream says this image is deprecated, unsupported, and should not be used. source
  • Deprecation and usage Deprecated, unsupported, and not updated; use only as a temporary nginx maintenance page. source

Fetched 4 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What ports should be exposed for the Maintenance image?

Expose container ports 80 and 443, for example as 80:80 and 443:443. You can map them to different host ports using normal Docker port mapping.

Does the Maintenance image try to import SWAG settings?

When it starts up, it will attempt to migrate from SWAG. You may need to change some Nginx settings for the container to start successfully.

How can an important reverse-proxy service stay accessible while the main web server is down?

Add the service proxy config file, such as proxy-confs/homeassistant.conf, to /config/includes.txt. The config is copied into the maintenance appdata, allowing that service to be accessed through the container.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads