Tim

The error messages you're seeing are from the local `ksync` container being unable to connect to the (also local) syncthing instance. Probably a local networking problem (if you running containers...

@jensenbox Thanks for pointing this out. I don't know anything about the name resolution differences, but we actually been working to eliminate compiling with `cgo` in order to get cross...

I'm doing some reading about it [here](https://engineering.grab.com/dns-resolution-in-go-and-cgo). I need to see if there's a good solution for this. In the meantime, compiling it yourself with that option should work.

Ok, I've read the above and I *think* I've got a handle on the problem. I think the "problem" is that go uses it's own internal name resolution mechanism (in...

For details, here's the difference between `/etc/resolv.conf` and `configd` on my system: /etc/resolv.conf ```shell cat /etc/resolv.conf # # macOS Notice # # This file is not consulted for DNS hostname...

@murich I'm not sure what you mean? What's being discussed here is an upstream problem with Go, specifically it's resolver package for native platforms. ~~I think since this issue was...

@eroldan It _should_ roll the container when new files are changed, are you saying manually editing files on the container side starts a reload loop? If so is it only...

Does this happen if you disable restarts when creating the spec?

I believe restart is a bool. I’ll check all of this in the morning

@eroldan I believe the correct command would be: ```shell ksync create --reload=false blah blah ```