Open ljavorsk opened 2 years ago
The same for me. I have hit the same issue. The lima looks good as a good alternative for me, but without supporting VPN it does not as I would wish for my work.
Nevertheless, good job with Lima, go ahead. If you need some more traces, just ask, like serial.log etc.
I had a similar issue with OpenVPN (tunnelblick). But the issue only happen when using vmnet (both shared and host). So my solution was to use shared and put a route in my provision script to go through the eth0 instead of the lima0 interface:
if [ ! -f /etc/sysconfig/network-scripts/route-eth0 ]; then
echo 10.0.0.0/8 via 192.168.5.2 dev eth0 > /etc/sysconfig/network-scripts/route-eth0
systemctl restart network.service
fi
Same issue here with rancher desktop implementation of lima. It is unable to connect use the VPN of the host.
This is the case with iVPN also. I have to disable the "firewall" of the VPN to allow lima to work.
I've integrated the lima software to my MacOS machine as described here: https://blog.carlosnunez.me/post/docker-desktop-alternative-for-mac/
The overall functionality is great, however, I've come across one big problem.
I use the Viscosity VPN to connect to our internal network, which is required by some tools I use in the container. But when I've moved from Docker Desktop to Lima this connection stopped working inside the container.
Does Lima support this? If so, should I change some configuration in order to solve this issue?
Thank you for help :)