lscr.io/linuxserver/quassel-web:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.https://$SERVER_IP:64443
. To setup this container you can either use the envrionment variables we recommend or manually setup the configuration file by leaving out the QUASSEL_CORE
environment variable among others. The configuration file using this method can be found at: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
)64443
-e
)PUID=1000
PGID=1000
QUASSEL_CORE=192.168.1.10
QUASSEL_PORT=4242
URL_BASE=/quassel
/quassel
-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 quassel-web /bin/bash
docker logs -f quassel-web
docker inspect -f '{{ index .Config.Labels "build_version" }}' quassel-web
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-web:latest