lscr.io/linuxserver/webtop:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.-e AUTO_LOGIN=false
.--security-opt seccomp=unconfined
setting to allow these syscalls or try podman as they have updated their codebase to support themstartwm.sh
executable script in their home directory. All of these containers are configured with passwordless sudo, we make no efforts to secure or harden these containers and we do not reccomend ever publishing their ports to the public Internet.--runtime=nvidia
and add an environment variable -e NVIDIA_VISIBLE_DEVICES=all
(can also be set to a specific gpu's UUID, this can be discovered by running nvidia-smi --query-gpu=gpu_name,gpu_uuid --format=csv
). NVIDIA automatically mounts the GPU and drivers from your host into the container.dtoverlay=vc4-fkms-v3d
in your usercfg.txt.<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
)3000
-e
)PUID=1000
PGID=1000
TZ=Europe/London
SUBFOLDER=/
/subfolder/
KEYBOARD=en-us-qwerty
-v
)/config
/var/run/docker.sock
--device
)/dev/dri
--shm-size=
--security-opt seccomp=unconfined
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 webtop /bin/bash
docker logs -f webtop
docker inspect -f '{{ index .Config.Labels "build_version" }}' webtop
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/webtop:latest