This message was deleted.

My reply to the guy above might be relevant if you're doing this through Kubernetes. If you're not and you're doing this through RD the only other thing to keep in mind is that it's running docker images on a VM, so you might get confusion between VM localhost vs host machine localhost so issues could still happen (even without the third layer of Kubernetes pods considering themselves to have another layer of localhost).

We just added a test for this, and it is failing for me when using the experimental tunneling networking mode with the moby engine: Add bats test for container published ports by Nino-K · Pull Request #5374 It works for me with containerd, and with both engines when using the current default networking. So I would need to get more information about your config to tell if this is the same issue or not.

Yes it is using the tunneling with Moby

@calm-sugar-3169 is working on it, but it may need to be fixed in 1.10

Oh…ok so there’s nothing we can do on our end?

I think we will need more info than the photo. Any repro instructions?

I mean it just happens on a fresh install of Rancher Desktop. Tried factory reset, unregistering the 2 distros but it only seems to create the rancher-desktop one. Reinstalling and restarting didn’t help.

Anything in the logs? Can you share the files in the log directory?

Is there a specific log that this would output to? It’s not my machine personally but happening to 3 people at our company

Can't tell off-hand; in a meeting now...

Ok

I don’t think there is one, would you kindly create one and feel free to assign it to me. Thanks

Ok I can, but I think I told @fast-garage-66093 before, I can’t assign it for some reason

Thanks! I assigned to Nino and updated all the metadata.

For the last issue I had, I found the cause. So on windows when you have GitBash installed, with the legacy console option checked, it causes Rancher to fail

Interesting! Can you file another Github issue?

Yep!