The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →To run Uptime Kuma on Fedora as a systemd-managed service, place a Quadlet .container file in the directory for your chosen mode, publish host port 3001 to container port 3001, and persist /app/data on local storage. Quadlet turns that file into an ordinary systemd service, so you start, stop, and inspect Uptime Kuma with systemctl rather than with manual podman run commands.
The Uptime Kuma project documents the container image and core runtime settings, and Podman documents how Quadlet generates services. The project does not publish a Quadlet file, so the unit in this guide is an adaptation of those documented settings. Validate it on your Fedora release before relying on it.
As an Amazon Associate I earn from qualifying purchases.
What you need before you start
- A Fedora host with Podman installed and a user with
sudorights (for rootful) or a dedicated service account (for rootless). - cgroup v2. Quadlet requires it. Check with
podman info --format {{.Host.CgroupsVersion}}; the output should bev2. - Local storage for the database. Uptime Kuma stores its SQLite database in
/app/data. The project states that POSIX file-lock support is required to avoid SQLite database corruption, and it warns about locking problems commonly seen with NFS. Use a directory on a local filesystem or a Podman volume. Do not place the database on NFS. - Port 3001 free on the host, or a different host port you are prepared to map.
You do not need Node.js, Git, or PM2. The project’s documentation lists those for its native, non-container installation path, which also names Fedora among supported distributions. The container path in this guide does not use them.
Choose rootful or rootless
Both modes use the same unit file. They differ in where the file lives, which systemd manager runs it, and which account owns the container.
#1 Best Overall
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKTEC WARRANTY - GMKtec offers a 3-year limited warranty (1 year replacement + 2 years parts replacement) for each mini PC, starting from the date of the purchase effective on all sales starting Oct. 2026. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC
| Aspect | Rootful (system service) | Rootless (user service) |
|---|---|---|
| Quadlet location | /etc/containers/systemd/ |
~/.config/containers/systemd/ of the service user |
| Reload and control | sudo systemctl daemon-reload, sudo systemctl start uptime-kuma.service |
systemctl --user daemon-reload, systemctl --user start uptime-kuma.service |
| Best fit | Host-level administration of the service | Keeping the container under a dedicated account’s service manager |
| Boot behavior | Managed by the system manager | Depends on the account’s user-manager setup (see the rootless steps below) |
| Volume path in the file | An absolute path such as /srv/uptime-kuma/data |
An absolute path inside the service user’s home, such as /home/kuma/uptime-kuma/data |
Write the Quadlet unit
Create uptime-kuma.container with the following content. Adjust only the volume path if your layout differs.
[Unit]
Description=Uptime Kuma monitoring
After=network-online.target
Wants=network-online.target
[Container]
Image=docker.io/louislam/uptime-kuma:2
ContainerName=uptime-kuma
PublishPort=3001:3001
Volume=/srv/uptime-kuma/data:/app/data:Z
[Service]
Restart=always
TimeoutStartSec=900
[Install]
WantedBy=default.target
What each part does:
Image=uses the project’s documentedlouislam/uptime-kuma:2image, written with its fully qualified registry name so Podman does not need to choose a registry. Check the project’s installation page at deployment time, because the recommended tag can change.PublishPort=3001:3001maps host port 3001 to container port 3001, the port the project documents. To use another host port, change only the left side, for examplePublishPort=8080:3001.Volume=binds a host directory to/app/data. The:Zoption relabels the directory for SELinux, which Fedora enforces by default. Use it only on a directory dedicated to Uptime Kuma, because the relabel applies to everything in that directory.TimeoutStartSec=900in the[Service]section gives the first start enough time to pull the image. The default systemd startup limit is 90 seconds.[Install]withWantedBy=default.targetis the documented Quadlet pattern for startup. Quadlet units are generated rather than enabled like ordinary static service files, so usestartand verify boot behavior after a reboot.
Rootful setup
- Create the data directory:
sudo mkdir -p /srv/uptime-kuma/data. - Create the unit:
sudo nano /etc/containers/systemd/uptime-kuma.containerand paste the file above. - Make systemd read the new file:
sudo systemctl daemon-reload. - Start the service:
sudo systemctl start uptime-kuma.service. - Confirm the state:
sudo systemctl status uptime-kuma.serviceshould showactive (running), andsudo podman psshould list theuptime-kumacontainer. - Open
http://localhost:3001on the host to reach the setup screen. - Reboot and run
systemctl is-active uptime-kuma.service. It should printactive.
Rootless setup
- Switch to the service account, for example
sudo -iu kuma. - Create the directories:
mkdir -p ~/.config/containers/systemd ~/uptime-kuma/data. - Create
~/.config/containers/systemd/uptime-kuma.containerwith the same content, changing the volume line to the absolute path, for exampleVolume=/home/kuma/uptime-kuma/data:/app/data:Z. - Reload the user manager:
systemctl --user daemon-reload. - Start the service:
systemctl --user start uptime-kuma.service, then check it withsystemctl --user status uptime-kuma.service. - For the service to run at boot without an interactive login, check that lingering is enabled for the account. Run
loginctl show-user kuma --property=Lingerand, if it reportsLinger=no, enable it from an administrator account withsudo loginctl enable-linger kuma. - Reboot and confirm with
systemctl --user is-active uptime-kuma.servicerun as that account.
Networking and reverse proxy
Local access on the host works with port 3001 published as shown. To reach Uptime Kuma from other machines, open the port in the firewall, for example sudo firewall-cmd --permanent --add-port=3001/tcp followed by sudo firewall-cmd --reload.
Rank #2
- [15W Ryzen 7 Agentic PC for Everyday Workflows] Powered by the AMD Ryzen 7 7730U processor (8 Cores, 16 Threads), the GEEKOM A5 is built for sustained productivity. It doubles as your cloud-native Agentic AI assistant, seamlessly hosting cloud AI tasks, automating office workflows, and handling intelligent document summarization without complex local deployment. Smoothly manage Microsoft Office, dozens of browser tabs, heavy Excel spreadsheets, and remote learning throughout your workday.
- [Smart Value Now, Expandable for Tomorrow] Equipped with 16GB RAM and a fast 256GB PCIe NVMe SSD for snappy daily performance, the A5 offers incredible value. Need more space later? It features dual-slot DDR4 RAM (upgradable to 64GB) and supports an M.2 SSD up to 4TB. With an extra M.2 2242 slot and 2.5" HDD bay for up to 10TB total storage, you get the flexibility to scale your storage seamlessly as your needs grow, beating soldered LPDDR solutions.
- [Multi-Display Connectivity for Maximum Productivity] Create a complete workstation with support for up to four displays through Dual HDMI and Dual USB-C ports, including up to 8K output via USB-C. Stay connected with Wi-Fi 6, Bluetooth 5.4, a 2.5GbE LAN port, SD card reader, and multiple USB ports for fast networking, efficient multitasking, and seamless connectivity across all your devices.
- [Built to Stay Cool, Quiet & Reliable] More than fast, the GEEKOM A5 is built to last. A reinforced one-piece all-metal internal frame enhances structural strength, while the upgraded IceBlast 3.0 cooling system improves cooling efficiency by up to 42% with up to 35% greater airflow for quieter operation. Backed by 339 reliability tests and a 72-hour full-load aging test, it's engineered for dependable long-term performance.
- 🏢[Business-Ready, Compact & Efficient] Pre-installed OS, the GEEKOM A5 supports Wake-on-LAN, Scheduled Power On, and Group Policy, making deployment and remote management simple for businesses. Its ultra-compact 0.6L design fits neatly behind monitors or into space-limited workstations while delivering excellent power efficiency for home offices, front desks, and commercial environments.
If you place Uptime Kuma behind a reverse proxy, forward the Upgrade and Connection headers. The project notes that the application uses WebSocket and needs them. Follow the project’s reverse-proxy guidance for your proxy’s syntax. A proxy is optional for a local-only deployment.
Updating the image
Back up /srv/uptime-kuma/data (or your rootless data directory) before upgrading. Then pull the current image and restart the unit:
Rank #3
- 【AMD Ryzen 3 5300U CPU: Outperforms N150 & 3500U】 BOSGAME E5 mini PC is powered by the TSMC 7nm FinFET architecture AMD Ryzen 3 5300U processor (4 Cores, 8 Threads, up to 3.8GHz boost, 6MB total cache). Compared to low-end Intel N150 or 3500U chips which only have 4 single threads and throttle under load, the 5300U delivers over 30% faster multi-core speed. Run 30+ browser tabs, large Excel sheets, and Zoom meetings simultaneously without system lag.
- 【8GB DDR4 RAM & 256GB NVMe SSD Storage】 Installed with high-speed 8GB DDR4 dual-channel memory and a fast 256GB M.2 2280 SSD, eliminating slow boot times and application loading delays. To accommodate growing data requirements, the upgradeable hardware design features dual SODIMM slots that allow you to expand memory up to 64GB RAM, ensuring smooth operation during heavy multitasking.
- 【High-Capacity Dual M.2 SSD Storage Expansion】 Never worry about running out of space for your business files. In addition to the pre-installed 256GB system drive, the motherboard houses an extra empty internal M.2 2280 NVMe PCIe 3.0 slot. This allows you to easily add a second solid-state drive for up to an additional 2TB of storage capacity (upgrades not included) without needing to remove or reinstall the original operating system.
- 【Radeon 6-Core Graphics & Triple 4K Displays】 Integrated with official AMD Radeon Graphics (6 Graphics Cores, 1500 MHz frequency) for casual gaming, photo editing, and crisp 4K media decoding. Featuring 1x HDMI 2.0 port, 1x DisplayPort, and 1x Full-Function Type-C port, the E5 outputs true 4K@60Hz resolution to three monitors at once. This multi-screen setup eliminates constant window-switching for traders, programmers, and office workers.
- 【Dual 2.5GbE LAN Ports for Advanced Networking】 Experience fast wired network transmission speeds up to 2500Mbps without lagging or buffering. The integration of dual 2.5 Gigabit Ethernet ports (powered by Realtek RTL8125 controller) makes this compact computer an exceptional hardware choice for tech enthusiasts. Easily configure it into software routers, hardware firewalls (pfSense, OpnSense), home NAS servers, or local homelabs.
sudo podman pull docker.io/louislam/uptime-kuma:2
sudo systemctl restart uptime-kuma.service
For rootless, run the same two commands as the service account, with systemctl --user in place of sudo systemctl and without sudo for podman.
Quick Recap
Rank #4
- This Certified Refurbished product is tested and certified to look and work like new. The refurbishing process includes functionality testing, basic cleaning, inspection, and repackaging. The product ships with all relevant accessories, a minimum 90-day warranty, and may arrive in a generic box. Only select sellers who maintain a high-performance bar may offer Certified Refurbished products on Amazon.com.
- Dell OptiPlex 7050 Micro Computer, Intel Quad Core i5-6500T up to 3.1GHz, 16G DDR4, 256G SSD.
- Includes: USB Keyboard & Mouse, Microsoft office 30 days free trail.
- Ports: 1 x RJ-45, 1 x HDMI, 1 x DP, 6 x USB 3.0.
- 4K Support: Support 4K (3840x2160) Dual display, makes it easy to connect two monitors at the same time, and you can expand working Windows, mirror content, or expand a single window across multiple monitors.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
Unit not found after systemctl start |
The file is in the wrong directory or has the wrong extension, or daemon-reload was skipped |
Confirm the path for your mode, check the .container extension, and run daemon-reload again |
| Start fails on the first run | The image pull exceeded systemd’s 90-second default startup limit | Pre-pull with podman pull, or increase TimeoutStartSec in the [Service] section |
| Quadlet does not generate a service | The host is not running cgroup v2 | Run podman info --format {{.Host.CgroupsVersion}} and resolve the cgroup version before continuing |
| Database errors or corruption | /app/data is on NFS or another filesystem without POSIX file-lock support |
Move the data to a local directory or Podman volume and restore from backup if needed |
Permission denied on /app/data |
The SELinux label is missing or the directory ownership does not match the container user | Keep :Z on a dedicated directory and check ownership of the host directory |
| Port 3001 already in use | Another service uses the host port | Change the host side of PublishPort=, for example 8080:3001 |
| Rootless service stops at logout or after reboot | Lingering is not enabled for the service account | Enable lingering with sudo loginctl enable-linger for that account |
| Live updates fail behind a proxy | Upgrade and Connection headers are not forwarded |
Add header forwarding in the proxy configuration |
> “”
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




