Issue with Launching WebAPI using Helm Charts

[shreyanssethi]

Expected behavior:
Trying to launch the ohdsi-Webapi on a minikube cluster and following the steps that are outlined here:
https://github.com/chgl/charts/tree/master/charts/ohdsi

The installation and update were successful but neither the atlas or webapi endpoint are working. Opening the minikube dashboard and going to the pods shows that all 3 pods (ohdsi-atlas, ohdsi-postgresql, and ohdsi-webapi) have errored with the falling error message:

"Failed to pull image "busybox:1.32": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.64.1:53: read udp 192.168.64.2:44156->192.168.64.1:53: i/o timeout"

Have tried deleting and reinstalling using Helm along with reinstalling Docker but neither has made any change.

Actual behavior
Once helm install is run and the endpoints are given, the WebAPI and Atlas should be running

Steps to reproduce behavior
https://github.com/chgl/charts/tree/master/charts/ohdsi
Follow the steps outlined here

[chgl]

"Failed to pull image "busybox:1.32": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 192.168.64.1:53: read udp 192.168.64.2:44156->192.168.64.1:53: i/o timeout"

This looks suspiciously like a DNS error where it is not able to resolve the docker.io domain and pull the busybox image. Maybe some of the suggestions at https://stackoverflow.com/questions/61094097/error-response-from-daemon-get-https-registry-1-docker-io-v2-dial-tcp-look are useful? If you're using MacOS, then maybe this applies as well: kubernetes/minikube#4012

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.