I need FUSE in my Domino Environment

I need to use FUSE based file storage

I need FUSE to work inside a Workspace

FUSE has been enabled in Domino 4.4.2 and later but will require a specific Environment and several options may need to be enabled.

Please see: https://docs.dominodatalab.com/en/latest/user_guide/0d73c6/domino-standard-environments/#_fuse_environment_flavors

The base images which activate FUSE can be found on quay.io (with a -fuse name extension) and these will include binaries needed to mount sshfs and Goofys binary for AWS bucket mounting.

A Central Config will be required to be added to see the /dev/fuse device:

A Feature Flag:

And these may also be required:

Once these are added, restart the nucleus services and a Workspace should display the /dev/fuse device. If this does not happen, or if workspaces fail to start simply remove the CC parameters and restart nucleus.

If you do get a running workspace, but no /dev/fuse, then your PSP/helm chart did not include the enablement for FUSE and an additional change needs to be done on your environment. Please contact your k8s team or Domino Team for further help.

tl;dr I still want FUSE without bothering the Domino Support team!

To make these changes to the deployer so that all executions contain the updated PSP in the agent.yaml, we recommend you reach out to your favourite platform engineer. However, in order to make this change to a single, existing deployment, you can follow the below commands (in a command line):

access your deployment (tsh/ssh/rancher/kube master):

kubectl get psp -A | grep nucleus -> find the correct compute grid nucleus pod
# (it usually ends in -cg2)
kubectl edit psp <nucleus-pod-ending-in-cg2>
# add: "- SYS_ADMIN" under "spec: allowedCapabilities".
# It normally would go under the capability "- NET_ADMIN"

Always beware of indentation when editing Yaml files! Domino will fail to save obviously incorrect yaml files, but you've been warned.