After initializing extra-tools containers, provisioner fails to start

[openmf]

After initializing extra-tools containers, provisioner fails to start

[israelzuniga]

Seems that also using the Kubernetes recipes the stack isn't going too far:

~ kubectl get pods --all-namespaces
NAMESPACE     NAME                                         READY   STATUS             RESTARTS   AGE
default       activemq-cluster-9d55db8c5-sd5jk             1/1     Running            0          18h
default       cassandra-cluster-75d97c649f-5hhlk           1/1     Running            0          18h
default       eureka-cluster-67f5f9998f-t7fgg              1/1     Running            0          18h
default       identity-ms-cluster-859dcbbff8-4pqqj         1/1     Running            28         18h
default       ledger-ms-cluster-788bd4fb6-f5g8f            0/1     ImagePullBackOff   0          18h
default       mariadb-cluster-d5cf99cb-8mddg               1/1     Running            0          18h
default       office-ms-cluster-59849bfbb7-5rvpd           0/1     ImagePullBackOff   0          18h
default       portfolio-ms-cluster-79484fb7b9-bkrnj        0/1     ImagePullBackOff   0          18h
default       provisioner-ms-cluster-6cdcbbf6d7-4r94g      1/1     Running            27         18h
default       rhythm-ms-cluster-86cfff7695-q9sxl           0/1     ImagePullBackOff   0          18h
docker        compose-74649b4db6-6m9xj                     1/1     Running            0          18h
docker        compose-api-64d6944ff-qtf64                  1/1     Running            0          18h
kube-system   etcd-docker-for-desktop                      1/1     Running            0          18h
kube-system   kube-apiserver-docker-for-desktop            1/1     Running            1          18h
kube-system   kube-controller-manager-docker-for-desktop   1/1     Running            0          18h
kube-system   kube-dns-86f4d74b45-n7z8c                    3/3     Running            0          18h
kube-system   kube-proxy-nvtc6                             1/1     Running            0          18h
kube-system   kube-scheduler-docker-for-desktop            1/1     Running            0          18h

Any ideas to solve this scenario?