-
Notifications
You must be signed in to change notification settings - Fork 371
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
"Unable to start portforwarding" #344
Comments
Thanks for reporting the issue, @selfagency - the issue occurs because Kubernetes cannot pull your image from Docker Hub (maybe because it is private?). If that is the case, you can create an imagePullSecret manually.. actually, a secret should have been created for you, but that did not seem to work. I will take a look and let you know when a fix is out for automatic pullSecret creation. |
Where/how do I create and specify the secret? Sorry, I rarely work with Docker. |
When your registry is private, you need to create a secret in Kubernetes containing an auth config for the private registry: https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/ However, I implemented a feature for automatic pull secret creation. Please, run |
this is on my laptop, with a fresh install of the new version
|
Seems like the image name is somehow wrong ('devspace' instead of 'selfagency/devspace'), therefore you can't push the image to dockerhub, because the name 'devspace' is forbidden. @selfagency Could you post your |
Closing this for now. Feel free to reopen this issue if the problem still exists. |
What happened?
Unable to start portforwarding: Unable to list devspace pods: Selected Pod(s) cannot start (Status: ImagePullBackOff)
What did you expect to happen instead?
For the dev space to launch
How can we reproduce the bug? (as minimally and precisely as possible)
Local Environment:
Kubernetes Cluster:
Anything else we need to know?
This is my first install and attempt at using devspace
/kind bug
The text was updated successfully, but these errors were encountered: