Thomas Hallgren
Thomas Hallgren
Are you using `sudo` or doing anything else that would affect the UID of the telepresence connector daemon?
Yes, that's normal. The root daemon is responsible network tunneling and DNS. It's not the one that mounts the filesystem. Can you see anything out of the ordinary in the...
There's nothing out of the ordinary in the logs. I have tried to reproduce the problem with different macOS versions (now on Monterey 12.3.1) and versions of macFUSE ranging from...
The `--port` cannot be repeated. Doing so would mean that the repetition must be grouped with `--service`. Also, different ports in a Deployment may use different containers, which in turn...
No, you're not doing anything wrong. You're hitting a limitation in the OSS-agent. It is only capable of doing one intercept at a time.
It will work correctly in 2.6.0 provided that you do `telepresence login` first. That too will change in the near future.
I notice these two lines in the output: ``` 2022-05-16 10:01:34.1382 error agent-injector : unable to get Ambassador Cloud preferred agent image: rpc error: code = Unauthenticated desc = transport:...
Yes, the configmap was introduced in the latest version.
If you upgrade and try again, it would be helpful if you could do: ``` $ telepresence loglevel debug $ telepresence gather-logs ``` and check if you find anything relevant...
So the telepresence agent is definitely using service port 80 and container port 80, and TCP. I can't think of anything that changes between 2.5.8 and 2.6.0 that would affect...