workspaces-issues
workspaces-issues copied to clipboard
Kasm blocking IP when started with Docker
Hey, i have a problem when i start Kasm on a Docker. Kasm is running but after a while it , i dont know how to describe it, it confuses other services. Then they get really laggy or are not reachable. (Not Ressource related, its a network issue)
I have double Nat with a Fritzbox and Unifi UDM Pro.
Fritzbox 192.168.99.1 UDM 192.168.2.1
Docker 192.168.2.13
So without Kasm i can ping all devices and access them without problems. If i start Kasm the Docker VM cant reach Fritzbox anymore. Then if i ping the Fritzbox it gets very strange this is the output i get if Kasm is started.
debian-docker:~# ping 192.168.99.1
PING 192.168.96.1 (192.168.96.1) 56(84) bytes of data.
i ping the right ip but the command switches to the internal kasm network ip that is generated from docker.
i tryed to add a different network but that did not help.
Something is really wrong. After a while other Services on the Docker become also very laggy with high ping or even unreachable. If i stop kasm and maybe deleate the network entry all is working fine again.
Somebody a idea?