lscr.io/linuxserver/fleet:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.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.<external>:<internal>
respectively. For example, -p 8080:80
would expose port 80
from inside the container to be accessible from the host's IP on port 8080
outside the container.-p
)8080
-e
)PUID=1000
PGID=1000
fleet_admin_authentication_type=DATABASE
fleet_database_url=jdbc:mariadb://<url>:3306/fleet
fleet_database_username=fleet_user
fleet_database_password=dbuserpassword
fleet_admin_secret=randomstring
-v
)/config
FILE__
.PASSWORD
based on the contents of the /run/secrets/mysecretpassword
file.-e UMASK=022
setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.-v
flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID
and group PGID
.PUID=1000
and PGID=1000
, to find yours use id user
as below:docker exec -it fleet /bin/bash
docker logs -f fleet
docker inspect -f '{{ index .Config.Labels "build_version" }}' fleet
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/fleet:latest