Join GitHub today
Failed to swap-deployment #848
What were you trying to do?
Run telepresence for the first time.
What did you expect to happen?
Telepresence to setup a remote pod and proxy the various "things".
What happened instead?
The pod was never successfully started. It was however created, just never finished starting.
The container logs :
Automatically included information
Looking through Dockerfile for the k8 proxy I'm not sure why you would:
Given that user 1000 will not be a part of the root group. It is bound to run in to a permission issue.
This looks like a pretty simple permission issue, but since I don't see an easy way to specify deployment details for the proxy pod, or a way to specify a custom image I'm not sure what a work around is.
I see in you allow a specific version of the docker image to be used (for testing) via an environmental arg, but no way to override the image entirely using --swap-deployment.
Fixing #723 will remedy this and #828. Your investigation has lead you to reasonable questions. The Dockerfiles are not particularly sensible; I threw them together quickly while fixing #617. The goal then was to avoid "securityContext: runAsUser: 0" as the way of running as root.
I'll be working on this soon and may send a test image your way via this issue. If you can try it on your cluster, that'd be great. Regardless, we'll get this taken care of for 0.95 this week. Thank you for your help.
@tcf909 Can you please try the