Skip to content
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

Container is not working "datawire/telepresence-k8s:0.99" #1027

Closed
JCzz opened this issue May 14, 2019 · 3 comments
Closed

Container is not working "datawire/telepresence-k8s:0.99" #1027

JCzz opened this issue May 14, 2019 · 3 comments
Labels
stale Issue is stale and will be closed

Comments

@JCzz
Copy link

JCzz commented May 14, 2019

update: Same on kubernetes

docker run --rm datawire/telepresence-k8s:0.99

Is giving the following error:

Unhandled Error
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/twisted/application/app.py", line 674, in run
    runApp(config)
  File "/usr/lib/python3.6/site-packages/twisted/scripts/twistd.py", line 25, in runApp
    runner.run()
  File "/usr/lib/python3.6/site-packages/twisted/application/app.py", line 381, in run
    self.application = self.createOrGetApplication()
  File "/usr/lib/python3.6/site-packages/twisted/application/app.py", line 453, in createOrGetApplication
    application = getApplication(self.config, passphrase)
--- <exception caught here> ---
  File "/usr/lib/python3.6/site-packages/twisted/application/app.py", line 464, in getApplication
    application = service.loadApplication(filename, style, passphrase)
  File "/usr/lib/python3.6/site-packages/twisted/application/service.py", line 416, in loadApplication
    application = sob.loadValueFromFile(filename, 'application')
  File "/usr/lib/python3.6/site-packages/twisted/persisted/sob.py", line 177, in loadValueFromFile
    eval(codeObj, d, d)
  File "./forwarder.py", line 62, in <module>
    main()
  File "./forwarder.py", line 53, in main
    with open(NAMESPACE_PATH) as f:
builtins.FileNotFoundError: [Errno 2] No such file or directory: '/var/run/secrets/kubernetes.io/serviceaccount/namespace'


Failed to load application: [Errno 2] No such file or directory: '/var/run/secrets/kubernetes.io/serviceaccount/namespace'

Setup:

docker version
Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:39 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.2
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.6
  Git commit:       6247962
  Built:            Sun Feb 10 04:13:06 2019
  OS/Arch:          linux/amd64
  Experimental:     false
@ark3
Copy link
Contributor

ark3 commented May 14, 2019

That docker run command is not expected to work. When you say "same on kubernetes," what do you mean? Can you show me what you're doing that's failing? Thanks!

If you want to experiment with that image, pass along a command to run:

$ docker run --rm -it datawire/telepresence-k8s:0.99 sh
~ $ ls
Dockerfile         periodic.py        requirements.txt   run.sh             test_forwarder.py
forwarder.py       podinfo.py         resolver.py        socks.py           test_socks.py
~ $ 

@JCzz
Copy link
Author

JCzz commented May 15, 2019

Thanks

I am trying to debug into a knative service, and I keep getting a CrashLoopBackOff. I then tried to run the image in docker. I did not expect to use sh when running the image.

knative service:

apiVersion: serving.knative.dev/v1alpha1
kind: Service
metadata:
  name: helloworld-go
  namespace: default
spec:
  runLatest:
    configuration:
      revisionTemplate:
        spec:
          container:
            image: datawire/telepresence-k8s:0.99

Sorry, it does actually work with your example from here

Any idea why not with Knative?

kubectl describe pod helloworld-go.. :
Back-off restarting failed container

@stale
Copy link

stale bot commented Apr 14, 2021

This issue has been automatically marked as stale because it has not had recent activity.
Issue Reporter: Is this still a problem? If not, please close this issue.
Developers: Do you need more information? Is this a duplicate? What's the next step?

@stale stale bot added the stale Issue is stale and will be closed label Apr 14, 2021
@JCzz JCzz closed this as completed Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue is stale and will be closed
Projects
None yet
Development

No branches or pull requests

2 participants