-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Port forwarding not working when official image is referenced #2066
Comments
Hey @demisx this behavior is currently expected -- only containers that contain images specified as skaffold artifacts will be port forwarded. We're working on adding user defined port-forwarding, which would allow you to specify additional containers to port-forward. Until that feature is fleshed out and merged, unfortunately this will continue to work as you've experienced. |
Got it. Thank you very much for your explanation. Would be really helpful if documentation page https://skaffold.dev/docs/how-tos/portforward/ mentioned this too. 👍 Shall I close this issue then? |
Agree that documentation would be helpful, would you be interested in submitting a PR? Feel free to close the issue as well, as it's effectively a dupe of #1311 |
Sure. I'll take a stab. I've created #2078 this PR with clarification added. Let me now if I need to add anything else. |
I can definitely take a stab at the PR. |
Expected behavior
Port forwarding should work no matter if the image is pulled directly from Docker hub or built locally
Actual behavior
Port forwarding works only if image is build locally.
Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: