linuxserver/fleet¶
Fleet provides an online web interface which displays a set of maintained images from one or more owned repositories.
Supported Architectures¶
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/fleet:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ✅ | arm64v8-<version tag> |
| armhf | ❌ |
Application Setup¶
Navigate to http://your_ip_here:8080 to display the home page. If DATABASE is selected as the preferred authentication process, ensure that you set up an initial user via http://your_ip_here:8080/setup. Once done, that page will no longer be available. A restart is preferable as it will remove the page altogether. Once complete, you can log into the app via http://your_ip_here:8080/login to manage your repositories.
Usage¶
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)¶
---
+ fleet - LinuxServer.io linuxserver/fleet¶
Fleet provides an online web interface which displays a set of maintained images from one or more owned repositories.
![fleet]()
Supported Architectures¶
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/fleet:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
Architecture Available Tag x86-64 ✅ amd64-<version tag> arm64 ✅ arm64v8-<version tag> armhf ❌
Application Setup¶
Navigate to http://your_ip_here:8080 to display the home page. If DATABASE is selected as the preferred authentication process, ensure that you set up an initial user via http://your_ip_here:8080/setup. Once done, that page will no longer be available. A restart is preferable as it will remove the page altogether. Once complete, you can log into the app via http://your_ip_here:8080/login to manage your repositories.
Usage¶
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)¶
---
version: "2.1"
services:
fleet:
@@ -59,4 +59,4 @@
--pull \
-t lscr.io/linuxserver/fleet:latest .
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Versions¶
- 12.07.23: - Rebase to Alpine 3.18.
- 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
- 02.05.22: - Rebase to Alpine 3.15.
- 13.12.21: - Add mitigations for CVE-2021-44228
- 26.04.20: - Updated to keep in line with v2.0.0 branch of Fleet
- 19.12.19: - Rebasing to alpine 3.11.
- 02.07.19: - Rebasing to alpine 3.10.
- 02.07.19: - Stop container if fleet fails.
- 19.05.19: - Use new base images for arm versions.
- 01.04.19: - Initial Release
Last update: October 13, 2023
Created: April 4, 2019
\ No newline at end of file
+Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Versions¶
- 12.07.23: - Rebase to Alpine 3.18.
- 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
- 02.05.22: - Rebase to Alpine 3.15.
- 13.12.21: - Add mitigations for CVE-2021-44228
- 26.04.20: - Updated to keep in line with v2.0.0 branch of Fleet
- 19.12.19: - Rebasing to alpine 3.11.
- 02.07.19: - Rebasing to alpine 3.10.
- 02.07.19: - Stop container if fleet fails.
- 19.05.19: - Use new base images for arm versions.
- 01.04.19: - Initial Release
Created: April 4, 2019