lscr.io/linuxserver/wireshark:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.NET_ADMIN
at a minimum, optionally you can use host networking to capture from your host level device or specify a Docker network you want to capture from.-p 3000:3000
.<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
--net
)--net=host
-e
)PUID=1000
PGID=1000
TZ=Europe/London
-v
)/config
cap_add
or sysctl
to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.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 wireshark /bin/bash
docker logs -f wireshark
docker inspect -f '{{ index .Config.Labels "build_version" }}' wireshark
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wireshark:latest