Platform For AI:Configure storage mounts for EAS services

Select a storage solution

To configure a storage mount, first select an underlying storage type, then choose a mounting method.

Basic storage mounts

{
  "storage": [
        {
            "oss": {
                "path": "oss://bucket/path/",
                "readOnly": false
            },
            "mount_path": "/mnt/data/"
        }
    ]
}

{
  "storage": [
        {
            "nfs": {
                "path": "/",
                "server": "06ba74****-a****.cn-hangzhou.nas.aliyuncs.com",
                "readOnly": false
            },
            "mount_path": "/mnt/data/"
        }
    ]
}

{
  "storage": [
        {
            "git": {
                "repo": "https://codeup.aliyun.com/xxx/eas/aitest.git",
                "branch": "master",
                "commit": "xxx",
                "username": "username",
                "password": "password or access token"
            },
            "mount_path": "/mnt/data/"
        }
    ]
}

Platform asset mounts

You can mount datasets, code sets, and models registered in PAI as AI Assets to your service instances. This enables centralized asset management and reuse.

"storage": [
        {
            "dataset": {
                "id": "d-pcsah1t86bm8******",
                "version": "v1",
                "read_only": false
            },
            "mount_path": "/mnt/data/"
        }
    ]

"storage": [
        {
            "code": {
                "id": "code-4d3b42a1152****"
            },
            "mount_path": "/mnt/data/"
        }
    ]

Advanced mounting options

EAS also supports the following advanced mounting methods:

• Image mount: Copies files from a specified path in a Docker image to a temporary local volume, then mounts it to the service instance. Large directories consume significant local storage and increase startup time. Use only when necessary.

• EmptyDir mount: Provides temporary local storage for a running instance. Content persists even if the instance restarts unexpectedly. Suitable for local caching or temporary file storage.

{
    "storage": [
        {
            "image": {
                "image": "registry-vpc.cn-xxxx.aliyuncs.com/eas/image_name:v1",
                "path": "/path/to/mount/"
            },
            "mount_path": "/data_image"
        }
    ]
}

{
    "storage": [
        {
            "empty_dir": {},
            "mount_path": "/mnt/temp"
        }
    ]
}

{
    "storage": [
        {
            "empty_dir": {
              "medium": "memory",
              "size_limit": 20
            },
            "mount_path": "/dev/shm"
        }
    ]
}

JSON configuration example

The following code provides a complete configuration example. For more information, see Deploy services by using JSON.

{
    "name": "service_name",
    "model_path": "http://path/to/model",
    "processor": "pmml",
    "storage": [
        {
            "oss": {
                "path": "oss://bucket/path/",
                "readOnly": false
            },
            "mount_path": "/mnt/oss_data/"
        },
        {
            "nfs": {
                "path": "/",
                "server": "06ba74****-a****.cn-hangzhou.nas.aliyuncs.com",
                "readOnly": false
            },
            "mount_path": "/mnt/nfs_data/"
        },
        {
            "image": {
                "image": "registry-vpc.cn-shanghai.aliyuncs.com/eas/test_image:v1",
                "path": "/path/to/mount/"
            },
            "mount_path": "/data_image"
        },
        {
            "empty_dir": {
              "medium": "memory",
              "size_limit": 20
            },
            "mount_path": "/dev/shm"
        },
        {
            "git": {
                "repo": "https://codeup.aliyun.com/xxx/eas/aitest.git",
                "branch": "master",
                "commit": "xxx",
                "username": "username",
                "password": "password or access token"
            },
            "mount_path": "/mnt/git_code/"
        }
    ],
    "metadata": {
        "cpu": 1,
        "instance": 1,
        "resource": "eas-r-xxx"
    }
}

FAQ

1. Why do I receive a "file not found" error after I mount an OSS bucket?

   This error is usually caused by an incorrect path. Check your mount configuration and access path.

   For example, if you mount oss://my-bucket/ to /mnt/data, the file at oss://my-bucket/subfolder/myfile.txt in OSS must be accessed from the path /mnt/data/subfolder/myfile.txt in the container, not /mnt/data/myfile.txt.

2. What do I do if a NAS mount fails due to a network connection issue?

   A NAS mount requires that the EAS service and the NAS mount target are in the same VPC. Check the following items:

   • VPC Consistency: Ensure the VPC ID is the same for both the EAS service and the NAS mount target.

   • Network Configuration: To access NAS, configure the network by following the instructions in Access public or internal resources from EAS.

   • Mount Target Status: Verify that the NAS mount target exists and is in the Available state.

3. What do I do if a Git mount fails due to an authentication error?

   Check the following configuration settings:

   • Access Token Validity: Confirm that your Git access token has not expired and has read permissions for the repository.

   • Repository Permissions: For a private repository, ensure that the username and password or token are correct and have read permissions.

   • Repository Address Format: Use the HTTPS protocol, such as https://github.com/user/repo.git. The Git protocol is not supported.

   • Branch/Commit Existence: Confirm that the specified branch name or commit ID exists in the repository.

4. What do I do if a service fails to start due to a mount path conflict?

   A mount path conflict can be caused by the following reasons:

   • Duplicate mount path: In the same service, multiple storage configurations use the same mount path. Ensure that the mount_path for each storage is unique.

   • System directory conflict: The mount path cannot be a critical system directory, such as /bin, /etc, /usr, or /lib. Use a path under /mnt or /data instead.

   • Incorrect Path Format: The mount path must be an absolute path that starts with a forward slash (/).

5. Can I use an FTP or SSH tool to connect to an instance to upload or download files?

   No. EAS instances do not provide FTP or SSH access.

6. Can I mount an OSS bucket that is in a different region from my EAS service?

   No. EAS cannot mount OSS buckets across regions. Use the cross-region replication feature of OSS to synchronize data to an OSS bucket in the same region as the EAS service.

7. If no storage is mounted, where are the files that I download to the instance stored?

   Files are saved to the instance's system disk, which is ephemeral. Data on the system disk is lost when the instance is restarted or updated. To persist data, mount external storage.