Access /dev/fuse in workspace containers

Access /dev/fuse in workspace containers to use fuse-overlayfs as a storage driver for Podman.

Before you begin

  • For OpenShift versions older than 4.15: you have administrator-enabled access to /dev/fuse. See Configuring fuse-overlayfs.
  • You have identified a workspace to use with fuse-overlayfs.

Procedure

Use the pod-overrides attribute to add the required annotations defined in Configuring fuse-overlayfs to the workspace. The pod-overrides attribute allows merging certain fields in the workspace pod’s spec.

For OpenShift versions older than 4.15: 

$ oc patch devworkspace <DevWorkspace_name> \
  --patch '{"spec":{"template":{"attributes":{"pod-overrides":{"metadata":{"annotations":{"io.kubernetes.cri-o.Devices":"/dev/fuse","io.openshift.podman-fuse":""}}}}}}}' \
  --type=merge

For OpenShift version 4.15 and later: 

$ oc patch devworkspace <DevWorkspace_name> \
  --patch '{"spec":{"template":{"attributes":{"pod-overrides":{"metadata":{"annotations":{"io.kubernetes.cri-o.Devices":"/dev/fuse"}}}}}}}' \
  --type=merge

Results

  1. Start the workspace and verify that /dev/fuse is available in the workspace container: 
    $ stat /dev/fuse

What to do next