# RKE2 - CSI for FlashArray not working **URL:** \ **Category:** Portworx on Kubernetes\ **Created:** [September 1, 2022, 7:47pm UTC](https://forums.portworx.com/t/rke2-csi-for-flasharray-not-working/1429 "2022-09-01T19:47:26Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ba-work](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/ba-work/32/613_2.png) [@ba-work](https://forums.portworx.com/u/ba-work)\ **Post date:** [September 1, 2022, 7:47pm UTC](https://forums.portworx.com/t/rke2-csi-for-flasharray-not-working/1429/1 "2022-09-01T19:47:26Z")
Generated a DaemonSet spec using 1.23.6+rke2r2, cloud, pure flasharray via FC. ([link](https://install.portworx.com/2.11?mc=false&kbver=1.23.6%2Brke2r2&oem=esse&user=0e1eb73e-09c4-4aa9-9cf5-7f2e1b06efc6&b=true&j=auto&pureSanType=FC&c=px-cluster-44ffacd3-508c-4b9b-9d83-9dc9a55c0fdb&stork=true&csi=true&tel=false&st=k8s®=%24%7Bregistry%7D)) The containerd socket is correctly detected/mounted (the k3s path) as seen in the spec Everything seems to deploy fine except the portworx container fails and logs this: ```auto time="2022-09-01T19:41:07Z" level=info msg="Input arguments: /px-oci-mon -c px-cluster-44ffacd3-508c-4b9b-9d83-9dc9a55c0fdb -a -secret_type k8s -j auto -b --oem esse -x kubernetes" time="2022-09-01T19:41:07Z" level=info msg="Updated arguments: /px-oci-mon -c px-cluster-44ffacd3-508c-4b9b-9d83-9dc9a55c0fdb -a -secret_type k8s -j auto -b -x kubernetes" install-opts=--upgrade time="2022-09-01T19:41:07Z" level=info msg="OCI-Monitor computed version v2.11.2-g4faee841-dirty" time="2022-09-01T19:41:07Z" level=info msg="REAPER: Starting ..." time="2022-09-01T19:41:07Z" level=info msg="Service handler initialized via as DBus{type:dbus,svc:portworx.service,id:0xc000889a00}" time="2022-09-01T19:41:07Z" level=info msg="Setting up container handler" time="2022-09-01T19:41:07Z" level=info msg="> run-host: /bin/sh -c cat /etc/crictl.yaml || cat /var/vcap/store/crictl.yaml" time="2022-09-01T19:41:07Z" level=warning msg="Could not retrieve my container ID (will search by labels)" error="Container not found" time="2022-09-01T19:41:07Z" level=info msg="Locating my container handler" time="2022-09-01T19:41:07Z" level=info msg="> Attempt to use Docker as container handler failed, trying next..." error="/var/run/docker.sock not a socket-file" time="2022-09-01T19:41:07Z" level=info msg="> Using ContainerD as container handler" time="2022-09-01T19:41:07Z" level=info msg="Activating REST server" time="2022-09-01T19:41:07Z" level=info msg="Activating node-watcher" time="2022-09-01T19:41:07Z" level=error msg="Could not extract my container's configuration: could not load container : container \"\" in namespace \"k8s.io\": not found" ``` I should add, the cluster is opearting normally and _I_ can find the container: ```auto root@node-1:/# export CRI_CONFIG_FILE=/var/lib/rancher/rke2/agent/etc/crictl.yaml root@node-1:/# /var/lib/rancher/rke2/bin/crictl ps -a CONTAINER IMAGE CREATED STATE NAME ATTEMPT POD ID d892498f255c2 35d7690fd305e 20 seconds ago Exited portworx 12 891b5be65501e b75e1da0b87f4 cb03930a2bd42 36 minutes ago Running csi-node-driver-registrar 0 891b5be65501e ``` Update: I attempted this with the 2.11 operator (which uses different/newer images for stork and autopilot than the 2.11 DaemonSet???) and I get the exact same error in the portworx container. ---
**Author:** ![sanjay.naikwadi](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sanjay.naikwadi/32/35_2.png) [@sanjay.naikwadi](https://forums.portworx.com/u/sanjay.naikwadi)\ **Post date:** [September 20, 2022, 5:18am UTC](https://forums.portworx.com/t/rke2-csi-for-flasharray-not-working/1429/2 "2022-09-20T05:18:39Z")
Can you share the output of `kubectl get nodes -o wide` ? Just wanted to confirm if you are running Ubuntu 22.04 LTS then its not supported yet, but there is a fix in plan for upcoming release. ---
**Author:** ![ba-work](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/ba-work/32/613_2.png) [@ba-work](https://forums.portworx.com/u/ba-work)\ **Post date:** [September 20, 2022, 7:20pm UTC](https://forums.portworx.com/t/rke2-csi-for-flasharray-not-working/1429/3 "2022-09-20T19:20:19Z")
They are on 20.04 ```nohighlight NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME node-1 Ready control-plane,etcd,master,worker 20d v1.23.6+rke2r2 10.102.16.241 10.102.17.241 Ubuntu 20.04.5 LTS 5.15.0-46-generic containerd://1.5.11-k3s2 node-2 Ready worker 20d v1.23.6+rke2r2 10.102.16.242 10.102.17.242 Ubuntu 20.04.5 LTS 5.15.0-46-generic containerd://1.5.11-k3s2 ``` ---
**Author:** ![sensre](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/sensre/32/299_2.png) [@sensre](https://forums.portworx.com/u/sensre)\ **Post date:** [September 22, 2022, 1:27pm UTC](https://forums.portworx.com/t/rke2-csi-for-flasharray-not-working/1429/4 "2022-09-22T13:27:48Z")
Run the k8s version lesser than v1.23.0. it would work. and also you may want to make sure on the supported [kernel version](https://docs.portworx.com/reference/supported-kernels/) as well. ---
**Author:** ![ba-work](https://yyz2.discourse-cdn.com/flex030/user_avatar/forums.portworx.com/ba-work/32/613_2.png) [@ba-work](https://forums.portworx.com/u/ba-work)\ **Post date:** [October 3, 2022, 3:38pm UTC](https://forums.portworx.com/t/rke2-csi-for-flasharray-not-working/1429/5 "2022-10-03T15:38:34Z")
Hey just a small update on this. The kubernetes version _was_ the problem. I’m on a version of 1.22 and it’s working great. As a recommendation, the spec generator in px-central should probably check for this. If you are already parsing the version to check for the presence of `+rke2/k3s` then checking for a maximum/minimum should also be in place. **[Also, (at the time of writing) this page directly states support for 1.23 and 1.24! That should probably be corrected or tested better.](https://docs.portworx.com/install-portworx/prerequisites/)**