-
-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
read-only telepresence version
#3193
Comments
Hi @nicks, the output we get is different, as below. Maybe the session was not quit and Telepresence took that command as a prompt to re-engage. Could you try running telepresence quit -s. That will stop it completely. Telepresence status works the same way by the way. |
Hi @cindymullins-dw ! Ah, I think I just realized what causes it. Try these repro steps:
My theory of what's happening is that telepresence gets into a weird state where the User Daemon is running but the Root Daemon is not, so |
Thanks, @nicks, not sure this is truly a bug but could probably be improved. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This was fixed some time ago. |
Please describe your use case / problem.
I have a health-checking script that reports if a user has the right version of telepresence installed.
Currently, if you run
telepresence version
when no daemons are running locally, telepresence tries to automatically start the daemon withsudo
. The user gets prompted for sudo.This is confusing to a user who doesn't expect a version-checking script to start background daemons or require admin access.
Describe the solution you'd like
Ideally, the default behavior of
telepresence version
wouldn't start up any new processes.Describe alternatives you've considered
Alternatively, I'd be fine with
telepresence version --read-only
that worked this way.Versions (please complete the following information)
Additional context
I have the same complaint about
telepresence status
The text was updated successfully, but these errors were encountered: