# linuxserver/fleet

linuxserver/fleet is a self-hosted development app. Fleet provides an online web interface which displays a set of maintained images from one or more owned repositories. It is open source and self-hosted, installable on ZimaOS and Docker Hub.

Canonical page: https://ourlocalhost.com/app/3897/linuxserver-fleet

## Description

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: ZimaOS.

## Health score

21/100 (Low), based on 3 of 4 factors.
- Maintained: 0 (GitHub repository no longer exists)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Light to run: 60 (2 GB minimum RAM, runs on ARM)

## Links

- GitHub: https://github.com/BigBearTechWorld/big-bear-casaos
- ZimaOS: https://github.com/bigbeartechworld/big-bear-casaos/tree/master/Apps/fleet
- Docker Hub: https://hub.docker.com/r/linuxserver/fleet

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/3897/linuxserver-fleet), the self-hosted and open-source app directory.
