Mounting file systems to a container

You can mount buckets and one ephemeral disk to Serverless Containers. To avoid data access errors, all mount points for ephemeral disks and buckets must be unique.

Mounting a bucket to a containerMounting a bucket to a container

Mounting buckets allows you to access them through the file system interface. In the container revision settings, the user can specify one or more mount paths. Use this path to access the directory in which the bucket is mounted. Do not use this path for anything other than an empty directory; otherwise, the container initialization may result in an error, and the mounted buckets will become unavailable.

You can mount the whole bucket or a specific folder.

The /run/storage_sync_socket path is reserved for the Unix socket. To avoid loss of information when reading/writing data from/to the bucket:

• Do not put anything in the Unix socket path destination.
• Do not read from the Unix socket or write to it.

To mount a bucket, the service account needs the following roles:

• storage.viewer to only read data from the bucket.
• storage.uploader to read and write data from/to the bucket.

Mounting an ephemeral diskMounting an ephemeral disk

To mount an ephemeral disk, you can specify a mount point. Use the specified path to access the directory in which the ephemeral disk is mounted. Do not use this path for anything other than an empty directory; otherwise, the container initialization may result in an error, and the mounted ephemeral disks will become unavailable. To mount the ephemeral disk correctly, provide the full absolute path to the mount point.

The ephemeral disk size is a multiple of 1 GB and is set in the range from 1 to 100 GB. The maximum size of the ephemeral disk at the Preview stage cannot exceed 100 GB.

An ephemeral disk of a given size is created when the container is called just before the user code is executed. It is formatted into the ext4 file system and mounted at the specified mount point.

The user code will have read-write access to the ephemeral disk throughout the container's lifetime.

If a container is called multiple times, there is a chance that its repeated calls will be processed by the same instance. In this case, the data remaining on the disk after the previous call can be accessed. Such container behavior is not determinated, and you cannot rely on the data being saved between calls.

See alsoSee also

• Mounting buckets to a function
• Mounting an ephemeral disk to a function
• Mounting buckets to a container
• Mounting an ephemeral disk to a container