Container can't start because /usr/local: read-only file system

[yaroslav-nakonechnikov]

Hello,

i've checked several tickets, and looks like it should be solved in #2125. but i can't find how to tell it to helm chart to use different directory.

This warning which i see in pod:

Warning  Failed  2m44s (x272 over 61m)  kubelet  (combined from similar events): Error: failed to generate container "dbb453b03b44474fd27761430e3d7e04959b88b08c1a780828d306b98882ecb7" spec: failed to apply OCI options: failed to mkdir "/usr/local": mkdir /usr/local: read-only file system

OS of the node: bottlerocket
Platform: EKS

yes, it is specific case, when we need access blob storage from AWS, but problem in the way to start driver itself.

Would be cool, if there some things will be added into values.yaml or at least mentioned, that only few OS's are going to work.

[yaroslav-nakonechnikov]

from what i understand now, it will not work, as on host (on bottelrocket), there is no support for systemd.
and this script tries to copy systemd service to host.

and same is for nfs... that sad :(

so, only one thing: request to add warning, that it will not work on bottlerocket (and other systems, where host OS doesn't have systemd)

[andyzhangx]

if systemd is not supported, you should set all env var in csi-blob-node daemonset as "false" to disable blobfuse-proxy:

            - name: INSTALL_BLOBFUSE_PROXY
              value: "true"
            - name: INSTALL_BLOBFUSE2
              value: "true"
            - name: SET_MAX_OPEN_FILE_NUM
              value: "true"
            - name: DISABLE_UPDATEDB
              value: "true"

[andyzhangx]

@yaroslav-nakonechnikov you could set following helm chart values as false during helm chart install:

node:
...
  enableBlobfuseProxy: true
  blobfuseProxy:
    installBlobfuse2: true
    setMaxOpenFileNum: true
    disableUpdateDB: true
    setReadAheadSize: true

[yaroslav-nakonechnikov]

but, with disabling blobfuse2 - what options left to access blobs?

I wanted to try this driver not to mess with NFS, and to work over fusefs mounts, but without blobfuse2 looks like it will not work at all.

[andyzhangx]

@yaroslav-nakonechnikov that's disabling blobfuse-proxy, so blobfuse mount would happen inside the blob csi driver, the issue is that if blob csi driver is restarted, existing blobfuse mount would be invalid, that's the reason why we use blobfuse-proxy to call blobfuse outside of blob csi driver pod, but in your case, blobfuse-proxy won't work, so just set enableBlobfuseProxy: false

[yaroslav-nakonechnikov]

@andyzhangx thank you! i'll try