Hello there friends! I have recently switched from...
# rancher-desktop
f
Hello there friends! I have recently switched from using docker desktop to Rancher. I'm having an issue where my container that previously could connect to an external web API can no longer do so with Rancher. Does anyone have any idea what the differences could be here?
w
so may need a bit more info like win/mac/linux, but my gut is that you may need a proxy? you can also test basic network connectivity by jumping into
rdctl shell
and making sure basic
curl
operations work. in case there is a vpn, dns tunnelling, or other environmental item you need to figure out
f
Hello. I am on Mac. After running bash in the container I can confirm that it has no network connectivity. Just some basic checking the /etc/hosts files are the exact same on them but the /etc/resolv.conf are a tad different. The one that isn't working contains a search site entry and their nameserver IPs are different.
w
so yeah seems like limavm may be having an issue moving traffic from the vm to the host. any security tooling in scope?
f
What do you mean by security tooling in scope?
w
vpn, firewall, av, etc. anything that might break the network bridging or cause packets to be lost
f
I am on a VPN and we have crowdstrike installed. But that's the case with both Docker Desktop and Rancher. They are both on my system that has both of tools. The rancher one can't reach anything including Google where the DD has no issues with any sites.
w
dd doesn't use limavm
did you try swapping between QEMU and VZ to see if things change?
i would see if https://lima-vm.io/docs/config/network/vmnet/ helps. maybe you are getting overlapping ip allocations or something. my gut says the vpn, but i don't think limavm has a gvproxy like option
i would try and get some ips from the host side and then try and connect to them using curl or whatever from the vm side. if the vpn is intercepting dns traffic than using the dns param for the limavm network config might work as well. hard ot guess what the issue is without some network info from the host and vm
f
Okay I will take a look at those. What kind of network info are you thinking? I obviously don't want to be posting my IPs out on the internet.
Well switching to QEMU lets the internet work. But now building my database SQL Server container fails, I'm assuming because of having to switch from virtiofs
w
Should just be a block device to the container. Will perform differently, but should still work. Emphasis on the should as there are always corner cases.
f
Yeah I don't know. This is driving me nuts.
Switching back to VZ and quitting the VPN still does not give me a network connection