You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/source/serve/advanced-guides/multi-app-container.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -167,3 +167,5 @@ If raylet is running inside a container, then that container needs the necessary
167
167
* This error should only occur when you're running the Ray cluster inside a container. If you see this error when starting the replica actor, try volume mounting `/var/lib/containers` in the container that runs raylet. That is, add `-v /var/lib/containers:/var/lib/containers` to the command that starts the Docker container.
168
168
***cannot clone: Operation not permitted; Error: cannot re-exec process**
169
169
* This error should only occur when you're running the Ray cluster inside a container. This error implies that you don't have the permissions to use Podman to start a container. You need to start the container that runs raylet, with privileged permissions by adding `--privileged`.
170
+
***Very slow or hanging container startup**
171
+
* This is typically caused by using the default podman storage driver (`vfs`) with large container images. Podman runs in rootless mode, so its startup sequence involves modifying permissions of files in the container. The default storage driver is very slow to do this. Try configuring podman to use the `overlay` storage driver instead. You may need to also configure the `mount_program` to point to `/usr/bin/fuse-overlayfs` (or your appropriate local path).
Copy file name to clipboardExpand all lines: python/ray/data/read_api.py
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4089,7 +4089,7 @@ def read_unity_catalog(
4089
4089
4090
4090
This function works by leveraging Unity Catalog's credential vending feature, which grants temporary, least-privilege
4091
4091
credentials for the cloud storage location backing the requested table or data files. It authenticates via the Unity Catalog
4092
-
REST API (Unity Catalog credential vending for external system access, `Databricks Docs <https://docs.databricks.com/en/data-governance/unity-catalog/credential-vending.html>`_),
4092
+
REST API (Unity Catalog credential vending for external system access, `Databricks Docs <https://docs.databricks.com/en/external-access/credential-vending.html>`_),
4093
4093
ensuring that permissions are enforced at the Databricks principal (user, group, or service principal) making the request.
4094
4094
The function supports reading data directly from AWS S3, Azure Data Lake, or GCP GCS in standard formats including Delta and Parquet.
0 commit comments