From 26b232cd44a70273e18b86420550d061b060b107 Mon Sep 17 00:00:00 2001 From: Jason Boxman Date: Wed, 4 Dec 2024 21:48:23 -0500 Subject: [PATCH] Add limitation regarding EFS file system - https://seqera.atlassian.net/browse/PLAT-997 --- platform_versioned_docs/version-24.2/data_studios/index.mdx | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/platform_versioned_docs/version-24.2/data_studios/index.mdx b/platform_versioned_docs/version-24.2/data_studios/index.mdx index 553a6cd9..4d6a8420 100644 --- a/platform_versioned_docs/version-24.2/data_studios/index.mdx +++ b/platform_versioned_docs/version-24.2/data_studios/index.mdx @@ -26,6 +26,10 @@ Before you get started, you need the following: Currently, Data Studios only supports AWS Batch compute environments that **do not** have Fargate enabled. ::: +## Limitations + +If you configured your AWS Batch compute environment to include an EFS file system with **EFS file system > EFS mount path**, the mount path cannot be the same as your work directory. When the work directory and EFS mount path are identical, the Data Studio snapshots fail causing a data studio instance to fail. For more information on AWS Batch configuration, see [AWS Batch][aws-batch]. + ## Container image templates Data Studios provides four container image templates: JupyterLab, RStudio Server, Visual Studio Code, and Xpra. The image templates install a very limited number of packages when the session container is built. You can install additional packages as needed during a session. @@ -108,5 +112,6 @@ The cleanup process is a best effort and not guaranteed. Seqera attempts to remo [vsc]: https://code.visualstudio.com/ [Wave]: https://seqera.io/wave/ +[aws-batch]: ../compute-envs/aws-batch.mdx [custom-envs]: ./custom-envs.mdx [build-status]: ./custom-envs.mdx#build-status