lscr.io/linuxserver/endlessh:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.LOGFILE
to true
and map a volume for /config
. The logs will be under /config/logs/endlessh
.<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
)2222
-e
)PUID=1000
PGID=1000
TZ=Europe/London
MSDELAY=10000
MAXLINES=32
MAXCLIENTS=4096
LOGFILE=false
true
, the log will be output to file under /config/logs/endlessh
(/config
needs to be mapped).BINDFAMILY=
4
or 6
to bind to IPv4 only or IPv6 only, respectively. Leave blank to bind to both.-v
)/config
LOGFILE
is set to true
.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 endlessh /bin/bash
docker logs -f endlessh
docker inspect -f '{{ index .Config.Labels "build_version" }}' endlessh
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/endlessh:latest