Issue Summary

CIFS share can't be used as a shared home with Confluence.

This is reproducible on Data Center:  Yes

Steps to Reproduce

1. Configure a CIFS share and mount it in the Confluence instance.
2. Start the Confluence v9.1.1 application using the CIFS share as its shared home.

   • docker run -d --name <container_name> -p 8090:8090 -v /dev/urandom:/dev/random -v <CIFS_SHARE_MOUNT>:/var/atlassian/application-data/shared-home atlassian/confluence:9.1.1
     

1. Access the Confluence UI in the browser to complete the setup.
2. The cluster setup fails with the following message.
   • 
3. Below are the logs captured in the atlassian-confluence.log file.

   • 2024-12-06 09:26:36,544 ERROR [http-nio-8090-exec-7] [confluence.setup.actions.SetupClusterAction] execute Could not setup cluster: 
      -- url: /setup/setupcluster.action | userName: anonymous | action: setupcluster | referer: <BASEURL>/setup/setupcluster-start.action | traceId: 00d4341bb43bfd85
     io.atlassian.util.concurrent.LazyReference$InitializationException: 	: Failed to acquire lock on secrets-config.yaml file.
     	at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156)
     ---
     Caused by: com.atlassian.secrets.api.SecretServiceException: Failed to acquire lock on secrets-config.yaml file.
     ---
     Caused by: java.io.IOException: No such file or directory
     

Actual Results

• Confluence setup can't be completed.

Expected Results

• The Clustering with Confluence Data Center document mentions that NFS and SMB/CIFS shares are supported as the locations of the shared directory. However, the Confluence setup fails with CIFS usage.

Workaround

• Currently, there is no workaround. Workaround will be added once found.