linuxserver/fleet
Fleet provides an online web interface which displays a set of maintained images from one or more owned repositories.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS
- 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.
21/100 Low
- Maintained
- 0GitHub repository no longer exists
- Popular
- No data
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 602 GB minimum RAM, runs on ARM
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 11 days ago
No GitHub repository data collected yet.
Checked 17 days ago - source: GitHub (BigBearTechWorld/big-bear-casaos)
Resources & Compatibility
Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Test Docker first Run `docker run hello-world` before starting Fleet to make sure Docker can run containers. If this does not finish successfully, the Fleet container will likely fail to start too. source
- Set PUID, PGID, and timezone In the container settings, set PUID/PGID (the user and group IDs the container runs as) to match the user that owns your files, and set TZ to your local timezone. Without this, files can end up with the wrong owner and cause permission errors, and times in logs may be off. source
- Save settings and use restart policy Map a host folder to /config inside the container so settings are kept, and set the restart policy to unless-stopped. If you skip this, deleting or updating the container can erase your setup, and it may not start automatically after a reboot. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What should I check if the Fleet container fails to start?
Run `docker run hello-world` first to confirm Docker can run containers. If that test fails, the Fleet container will likely fail to start too.
Which user and timezone settings should I set to avoid permission and log-time problems?
Set PUID and PGID to match the user that owns your files, and set TZ to your local timezone. Without this, files can end up with the wrong owner and log times may be off.
How should I keep settings when the container is deleted or updated?
Map a host folder to /config inside the container so settings are kept. If you skip this, deleting or updating the container can erase your setup.
What restart policy should I use?
Set the restart policy to unless-stopped. This helps the container start automatically after a reboot.
Answers sourced from github.com, github.com
Community
- Is something up with LinuxServer.io? : r/selfhosted - Reddit (reddit)
- LinuxServer.io (forum)
- looking for a very simple fleet management : r/selfhosted - Reddit (reddit)
Collected 47 days ago - public community threads