lscr.io/linuxserver/kanzi:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags./config
directory of the docker container docker exec -itw /config kanzi bash
lexigram login --no-browser true
to setup your AWS credentials and copy the URL into a browser, login to your Amazon Developer Account and copy/paste the resulting authorisation code back into the terminal and press enter.kodi.config
according to your local setup and this will be used by the included gunicorn server to respond to requests.https
. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.<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
)8000
-e
)PUID=1000
PGID=1000
TZ=Europe/London
INVOCATION_NAME=kanzi
URL_ENDPOINT=https://server.com/kanzi/
https://kanzi.server.com/
or https://server.com/kanzi/
Note the trailing slash MUST be included.-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 kanzi /bin/bash
docker logs -f kanzi
docker inspect -f '{{ index .Config.Labels "build_version" }}' kanzi
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/kanzi:latest