Repository navigation
[BUG] iproute2 seems to be missing in webtop:ubuntu-xfce #439
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Trying lscr.io/linuxserver/webtop:ubuntu-xfce using host-network enabled at the host.
-
No obvious way to edit files through CLI. Workaround is to use Thunar and navigate to the file and then use Mousepad to edit it.
-
I fail to locate on how to properly set a default gateway to be used. Turns out that iproute2 package is missing? Or is there some other way to configure default gateway in webtop:ubuntu-xfce?
Expected Behavior
-
vi and/or nano should exist.
-
iproute2 should exist so one can use "ip" commands to see and alter network settings such as default gateway to be used.
Steps To Reproduce
- Using VyOS Stream 2026.03 as host.
- Using this config for webtop:ubuntu-xfce:
set container name webtop allow-host-networks
set container name webtop environment LC_ALL value 'sv_SE.UTF-8'
set container name webtop environment PGID value '102'
set container name webtop environment PUID value '0'
set container name webtop environment TZ value 'Europe/Stockholm'
set container name webtop image 'lscr.io/linuxserver/webtop:ubuntu-xfce'
set container name webtop memory '16384'
set container name webtop restart 'on-failure'
set container name webtop volume config destination '/config'
set container name webtop volume config source '/config/container/webtop/config'
- Works as expected except for no obvious way to edit files through CLI or to change default gateway to be used by this container since having host-networking enabled.
Environment
- OS: VyOS Stram 2026.03
- How docker service was installed:
set container name webtop allow-host-networks
set container name webtop environment LC_ALL value 'sv_SE.UTF-8'
set container name webtop environment PGID value '102'
set container name webtop environment PUID value '0'
set container name webtop environment TZ value 'Europe/Stockholm'
set container name webtop image 'lscr.io/linuxserver/webtop:ubuntu-xfce'
set container name webtop memory '16384'
set container name webtop restart 'on-failure'
set container name webtop volume config destination '/config'
set container name webtop volume config source '/config/container/webtop/config'CPU architecture
x86-64
Docker creation
Using image from: lscr.io/linuxserver/webtop:ubuntu-xfceContainer logs
No relevant logs.
Activity
github-actions commentedon Jul 21, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
j0nnymoe commentedon Jul 21, 2026
Not having used VyOS but when using docker run / compose, you would set any networking configuration on the container itself or if using host, docker gives the container the host network interface details.
thelamer commentedon Jul 21, 2026
I don't document or recommend using host networking. I guess you could there are a bunch of settings to parse through to customize all the ports to avoid conflicts:
https://github.com/linuxserver/docker-webtop#options-in-all-selkies-based-gui-containers
Need to customize all three custom ports.
As far as installing iproute2
As far as getting iproute2 into the baseimage for ubunturesolute:
https://github.com/linuxserver/docker-baseimage-selkies/issues
Apachez- commentedon Jul 21, 2026
Thanks!
Using host-network is just a workaround since the host is using VRFs which currently seems to cause issue with regular port-mappings:
https://vyos.dev/T9110
That is I can from another client at VRF PROD connect to this container successfully.
Its just that this container fails to connect to the internet (available at VRF PROD).
Could be due to that DNS-queries uses UDP and for that to work properly with VRFs you need to bind to device like 192.168.1.20%PROD where the container itself doesnt do that.
Thanks for the workaround of how to dynamically add iproute2 to this image will see if that someone can resolve (or at least workaround) my current issues.
Apachez- commentedon Jul 21, 2026
I tried with both:
and
But in both cases Im getting this log when connecting to https://192.168.1.20:3001
However the image is preloaded at the host:
Could it be that DOCKER_MODS isnt compatible with podman (which VyOS uses instead of docker)?
thelamer commentedon Aug 11, 2026
ip is in all containers