Why the Can Error Occur

• Databricks now sets the environment variable GIT_CONFIG_GLOBAL=/Workspace/.proc/self/git/config in notebooks and web terminals, so when you run any git --global command, Git tries to read/write the config at that path.
• On some cluster types (especially serverless and web terminal):
  • Databricks automatically sets up this virtual config file using workspace file system (WSFS)—but only if the right supporting services and preview features are enabled for your workspace and cluster type.
  • If the supporting back-end (CP APIs, WSFS, or feature flags) isn’t available or not yet rolled out in your environment, that virtual config file simply doesn’t exist—resulting in the "No such file or directory" locking error.
• This also happens on some free-tier or newer workspaces where the data plane-to-control plane integration for the Git config has not been fully configured or enabled yet

Tell me more about your environment? Are you on community edition?  Are you a customer of Databricks?

Louis