lscr.io/linuxserver/syslog-ng:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags./config/syslog-ng.conf
to configure your logging sources and destinations. Note: As the application does not run as root you cannot listen on ports < 1024.<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
)5514/udp
6601/tcp
6514/tcp
-e
)PUID=1000
PGID=1000
TZ=Europe/London
-v
)/config
/var/log
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 syslog-ng /bin/bash
docker logs -f syslog-ng
docker inspect -f '{{ index .Config.Labels "build_version" }}' syslog-ng
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/syslog-ng:latest