gthvidsten edited a comment on issue #381: URL: https://github.com/apache/solr-operator/issues/381#issuecomment-984666776
Thanks for the swift reply :) I tried doing a `kubectl port-forward` to my "example-solrcloud-common" (8080 -> 80), but when I access http://localhost:8080 I get the following error in the shell: ``` Handling connection for 8080 E1202 15:12:11.516200 32672 portforward.go:400] an error occurred forwarding 8080 -> 8983: error forwarding port 8983 to pod 8a8abe2427d899d7e84f2e524fc43747d9e05ba49d23eda7bf263f731e66d6fa, uid : failed to execute portforward in network namespace "/var/run/netns/cni-8c979efc-93e7-93a6-a2fb-a78a8185e794": failed to dial 8983: dial tcp4 127.0.0.1:8983: connect: connection refused ``` EDIT: On second thought, that might be because my solr containers aren't starting. It seems there's a problem pulling a specific image: `library/busybox:1.28.0-glibc` This is not an image that is present in our Container Registry, nor does that name include a FQDN in the image name... so I guess the problem is the Helm Chart setting up a Pod to require this image, but it is non-existing in our environment? It seems there's a similar problem for the Zookeeper Pods, but for a different image: `pravega/zookeeper:0.2.13` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
