You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to setup Portworx Essentials operator in okd 4.10.0-0.okd-2022-04-23-131357. The cluster is running in VMware/Vcenter 6.7.
I'm installing the operator from okd operator hub, see below. When I try to create the storage cluster, see below the pods get stuck in a crash loop, see below
Below is the message in the pod event log.
Generated from portworx
Could not talk to Docker/Containerd/CRI: Could not determine my container ID: Container not found - please ensure '/var/run/docker.sock', '/run/containerd/containerd.sock' or '/var/run/crio/crio.sock' are mounted.
This is the Kubernetes Version I'm running:
kubectl version --short | awk -Fv '/Server Version: / {print $3}'
WARNING: version difference between client (0.23) and server (1.23) exceeds the supported minor version skew of +/-1
1.23.5-rc.0.2062+9ce5071670476d-dirty
What am I'm missing?
The text was updated successfully, but these errors were encountered:
Trying to setup Portworx Essentials operator in okd 4.10.0-0.okd-2022-04-23-131357. The cluster is running in VMware/Vcenter 6.7.
I'm installing the operator from okd operator hub, see below. When I try to create the storage cluster, see below the pods get stuck in a crash loop, see below
Below is the message in the pod event log.
Generated from portworx
Could not talk to Docker/Containerd/CRI: Could not determine my container ID: Container not found - please ensure '/var/run/docker.sock', '/run/containerd/containerd.sock' or '/var/run/crio/crio.sock' are mounted.
This is the Kubernetes Version I'm running:
kubectl version --short | awk -Fv '/Server Version: / {print $3}'
WARNING: version difference between client (0.23) and server (1.23) exceeds the supported minor version skew of +/-1
1.23.5-rc.0.2062+9ce5071670476d-dirty
What am I'm missing?
The text was updated successfully, but these errors were encountered: