Trying to install Prometheus on minikube with docker driver

I am very new to Kubernetes and Docker and I have to study them for a master’s thesis.
I have created a CentOS 8 minimal VM on Windows using VirtualBox and I have installed Docker and Minikube. So now, I’m trying to install Prometheus from stable repository (https://kubernetes-charts.storage.googleapis.com) using Helm 3, however after install its I have always the same situation:

[[email protected] ~]$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                            READY   STATUS              RESTARTS   AGE
default       prometheus-alertmanager-74755454f6-dd4dz        0/2     ContainerCreating   0          38s
default       prometheus-kube-state-metrics-95d956569-h49wg   0/1     ContainerCreating   0          38s
default       prometheus-node-exporter-972gs                  0/1     ImagePullBackOff    0          38s
default       prometheus-pushgateway-594cd6ff6b-ftzhp         0/1     ContainerCreating   0          38s
default       prometheus-server-7bc886d65-mxcxg               0/2     ContainerCreating   0          38s
kube-system   coredns-f9fd979d6-jq6nk                         1/1     Running             0          72s
kube-system   etcd-minikube                                   0/1     Running             0          71s
kube-system   kube-apiserver-minikube                         1/1     Running             0          71s
kube-system   kube-controller-manager-minikube                1/1     Running             0          71s
kube-system   kube-proxy-4c7fk                                1/1     Running             0          72s
kube-system   kube-scheduler-minikube                         1/1     Running             0          71s
kube-system   storage-provisioner                             1/1     Running             1          76s
[[email protected] ~]$ 

Which becomes after some minutes:

[[email protected] ~]$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                            READY   STATUS             RESTARTS   AGE
default       prometheus-alertmanager-74755454f6-dd4dz        0/2     ErrImagePull       0          6m7s
default       prometheus-kube-state-metrics-95d956569-h49wg   0/1     ImagePullBackOff   0          6m7s
default       prometheus-node-exporter-972gs                  0/1     ImagePullBackOff   0          6m7s
default       prometheus-pushgateway-594cd6ff6b-ftzhp         0/1     ErrImagePull       0          6m7s
default       prometheus-server-7bc886d65-mxcxg               0/2     ErrImagePull       0          6m7s
kube-system   coredns-f9fd979d6-jq6nk                         1/1     Running            0          6m41s
kube-system   etcd-minikube                                   1/1     Running            0          6m40s
kube-system   kube-apiserver-minikube                         1/1     Running            0          6m40s
kube-system   kube-controller-manager-minikube                1/1     Running            0          6m40s
kube-system   kube-proxy-4c7fk                                1/1     Running            0          6m41s
kube-system   kube-scheduler-minikube                         1/1     Running            0          6m40s
kube-system   storage-provisioner                             1/1     Running            1          6m45s

So I ran kubectl describe pod prometheus-node-exporter-972gs, and I have these events:

Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  7m45s                  default-scheduler  Successfully assigned default/prometheus-node-exporter-972gs to minikube
  Warning  Failed     7m34s                  kubelet            Failed to pull image "prom/node-exporter:v1.0.1": 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.49.1:53: read udp 192.168.49.2:36409->192.168.49.1:53: i/o timeout
  Warning  Failed     6m14s                  kubelet            Failed to pull image "prom/node-exporter:v1.0.1": 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.49.1:53: read udp 192.168.49.2:59771->192.168.49.1:53: i/o timeout
  Warning  Failed     4m54s                  kubelet            Failed to pull image "prom/node-exporter:v1.0.1": 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.49.1:53: read udp 192.168.49.2:56617->192.168.49.1:53: i/o timeout
  Normal   Pulling    4m1s (x4 over 7m44s)   kubelet            Pulling image "prom/node-exporter:v1.0.1"
  Warning  Failed     3m24s (x4 over 7m34s)  kubelet            Error: ErrImagePull
  Warning  Failed     3m24s                  kubelet            Failed to pull image "prom/node-exporter:v1.0.1": 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.49.1:53: read udp 192.168.49.2:35763->192.168.49.1:53: i/o timeout
  Warning  Failed     2m56s (x7 over 7m33s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    2m42s (x8 over 7m33s)  kubelet            Back-off pulling image "prom/node-exporter:v1.0.1"

At this moment, I tried to check if minikube could connect to the internet, so I have done minikube ssh and I ran sudo apt-get update, but this is the output:

[email protected]:~$ sudo apt-get update
Err:1 http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.18:/1.18.3/xUbuntu_20.04  InRelease         
  Temporary failure resolving 'download.opensuse.org'
Err:2 http://archive.ubuntu.com/ubuntu focal InRelease                                                                                    
  Temporary failure resolving 'archive.ubuntu.com'
Err:3 http://security.ubuntu.com/ubuntu focal-security InRelease                                        
  Temporary failure resolving 'security.ubuntu.com'
Err:4 https://dl.bintray.com/afbjorklund/podman focal InRelease                                         
  Temporary failure resolving 'dl.bintray.com'
Err:5 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Err:6 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Temporary failure resolving 'archive.ubuntu.com'
Reading package lists... Done        
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease  Temporary failure resolving 'archive.ubuntu.com'
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease  Temporary failure resolving 'security.ubuntu.com'
W: Failed to fetch http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable:/cri-o:/1.18:/1.18.3/xUbuntu_20.04/InRelease  Temporary failure resolving 'download.opensuse.org'
W: Failed to fetch https://dl.bintray.com/afbjorklund/podman/dists/focal/InRelease  Temporary failure resolving 'dl.bintray.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.

It’s like minikube has no internet connection.
If someone knows how to solve this problem, please help me. I use a SSH connection to work on CentOS terminal, Docker should correctly works and I have installed minikube with docker driver, this is the output when I start it:

[[email protected] ~]$ minikube start
?  minikube v1.14.0 on Centos 8.2.2004
✨  Automatically selected the docker driver
?  Starting control plane node minikube in cluster minikube
?  Creating docker container (CPUs=2, Memory=2200MB) ...
❗  This container is having trouble accessing https://k8s.gcr.io
?  To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
?  Preparing Kubernetes v1.19.2 on Docker 19.03.8 ...
?  Verifying Kubernetes components...
?  Enabled addons: default-storageclass, storage-provisioner
?  Done! kubectl is now configured to use "minikube" by default

Thanks

P.S.

I just run systemctl status docker and it prints this:

● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2020-10-13 13:46:13 CEST; 1min 9s ago
     Docs: https://docs.docker.com
 Main PID: 1145 (dockerd)
    Tasks: 12
   Memory: 150.1M
   CGroup: /system.slice/docker.service
           └─1145 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

ott 13 13:46:11 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:11.801321705+02:00" level=warning msg="Your kernel does not support cgroup blkio weight_device"
ott 13 13:46:11 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:11.801455663+02:00" level=info msg="Loading containers: start."
ott 13 13:46:12 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:12.883288116+02:00" level=info msg="Removing stale sandbox c62e195b76598d7ed8215350c5565f83a73667854fac82703c5607399a104ef3 (5dc0dce7b3524555d5563c591108c0696659>
ott 13 13:46:13 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:13.162109412+02:00" level=warning msg="Error (Unable to complete atomic operation, key modified) deleting object [endpoint b430da4d189ecd1bce1a72429769288b14799b>
ott 13 13:46:13 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:13.601597872+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP >
ott 13 13:46:13 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:13.809031364+02:00" level=info msg="Loading containers: done."
ott 13 13:46:13 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:13.848966125+02:00" level=info msg="Docker daemon" commit=4484c46d9d graphdriver(s)=overlay2 version=19.03.13
ott 13 13:46:13 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:13.849071857+02:00" level=info msg="Daemon has completed initialization"
ott 13 13:46:13 localhost.localdomain dockerd[1145]: time="2020-10-13T13:46:13.874474316+02:00" level=info msg="API listen on /var/run/docker.sock"
ott 13 13:46:13 localhost.localdomain systemd[1]: Started Docker Application Container Engine.

Source: Docker Questions