dstack 0.19.6rc1__tar.gz → 0.19.7__tar.gz

dstack-0.19.7/.justfile

@@ -0,0 +1,17 @@
+# Root justfile
+#
+# This justfile serves as the main entry point to recipes from different components.
+#
+# Run `just` to see all available commands.
+#
+# Components:
+# * runner/justfile – Building and uploading dstack runner and shim
+
+default:
+    @just --list
+
+set allow-duplicate-recipes
+
+import "runner/.justfile"
+
+# TODO: Add frontend/justfile for managing frontend development tasks

{dstack-0.19.6rc1 → dstack-0.19.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dstack
-Version: 0.19.6rc1
+Version: 0.19.7
 Summary: dstack is an open-source orchestration engine for running AI workloads on any cloud or on-premises.
 Project-URL: Homepage, https://dstack.ai
 Project-URL: Source, https://github.com/dstackai/dstack
@@ -21,7 +21,7 @@ Requires-Dist: cryptography
 Requires-Dist: cursor
 Requires-Dist: filelock
 Requires-Dist: gitpython
-Requires-Dist: gpuhunt<0.2.0,>=0.1.3
+Requires-Dist: gpuhunt==0.1.5
 Requires-Dist: jsonschema
 Requires-Dist: packaging
 Requires-Dist: paramiko>=3.2.0
@@ -52,6 +52,7 @@ Requires-Dist: azure-mgmt-compute>=29.1.0; extra == 'all'
 Requires-Dist: azure-mgmt-network<28.0.0,>=23.0.0; extra == 'all'
 Requires-Dist: azure-mgmt-resource>=22.0.0; extra == 'all'
 Requires-Dist: azure-mgmt-subscription>=3.1.1; extra == 'all'
+Requires-Dist: backports-entry-points-selectable; extra == 'all'
 Requires-Dist: boto3; extra == 'all'
 Requires-Dist: botocore; extra == 'all'
 Requires-Dist: datacrunch; extra == 'all'
@@ -87,6 +88,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'aws'
 Requires-Dist: alembic>=1.10.2; extra == 'aws'
 Requires-Dist: apscheduler<4; extra == 'aws'
 Requires-Dist: asyncpg; extra == 'aws'
+Requires-Dist: backports-entry-points-selectable; extra == 'aws'
 Requires-Dist: boto3; extra == 'aws'
 Requires-Dist: botocore; extra == 'aws'
 Requires-Dist: docker>=6.0.0; extra == 'aws'
@@ -117,6 +119,7 @@ Requires-Dist: azure-mgmt-compute>=29.1.0; extra == 'azure'
 Requires-Dist: azure-mgmt-network<28.0.0,>=23.0.0; extra == 'azure'
 Requires-Dist: azure-mgmt-resource>=22.0.0; extra == 'azure'
 Requires-Dist: azure-mgmt-subscription>=3.1.1; extra == 'azure'
+Requires-Dist: backports-entry-points-selectable; extra == 'azure'
 Requires-Dist: docker>=6.0.0; extra == 'azure'
 Requires-Dist: fastapi; extra == 'azure'
 Requires-Dist: grpcio>=1.50; extra == 'azure'
@@ -139,6 +142,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'datacrunch'
 Requires-Dist: alembic>=1.10.2; extra == 'datacrunch'
 Requires-Dist: apscheduler<4; extra == 'datacrunch'
 Requires-Dist: asyncpg; extra == 'datacrunch'
+Requires-Dist: backports-entry-points-selectable; extra == 'datacrunch'
 Requires-Dist: datacrunch; extra == 'datacrunch'
 Requires-Dist: docker>=6.0.0; extra == 'datacrunch'
 Requires-Dist: fastapi; extra == 'datacrunch'
@@ -170,6 +174,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'gcp'
 Requires-Dist: alembic>=1.10.2; extra == 'gcp'
 Requires-Dist: apscheduler<4; extra == 'gcp'
 Requires-Dist: asyncpg; extra == 'gcp'
+Requires-Dist: backports-entry-points-selectable; extra == 'gcp'
 Requires-Dist: docker>=6.0.0; extra == 'gcp'
 Requires-Dist: fastapi; extra == 'gcp'
 Requires-Dist: google-api-python-client>=2.80.0; extra == 'gcp'
@@ -199,6 +204,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'kubernetes'
 Requires-Dist: alembic>=1.10.2; extra == 'kubernetes'
 Requires-Dist: apscheduler<4; extra == 'kubernetes'
 Requires-Dist: asyncpg; extra == 'kubernetes'
+Requires-Dist: backports-entry-points-selectable; extra == 'kubernetes'
 Requires-Dist: docker>=6.0.0; extra == 'kubernetes'
 Requires-Dist: fastapi; extra == 'kubernetes'
 Requires-Dist: grpcio>=1.50; extra == 'kubernetes'
@@ -222,6 +228,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'lambda'
 Requires-Dist: alembic>=1.10.2; extra == 'lambda'
 Requires-Dist: apscheduler<4; extra == 'lambda'
 Requires-Dist: asyncpg; extra == 'lambda'
+Requires-Dist: backports-entry-points-selectable; extra == 'lambda'
 Requires-Dist: boto3; extra == 'lambda'
 Requires-Dist: botocore; extra == 'lambda'
 Requires-Dist: docker>=6.0.0; extra == 'lambda'
@@ -246,6 +253,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'nebius'
 Requires-Dist: alembic>=1.10.2; extra == 'nebius'
 Requires-Dist: apscheduler<4; extra == 'nebius'
 Requires-Dist: asyncpg; extra == 'nebius'
+Requires-Dist: backports-entry-points-selectable; extra == 'nebius'
 Requires-Dist: docker>=6.0.0; extra == 'nebius'
 Requires-Dist: fastapi; extra == 'nebius'
 Requires-Dist: grpcio>=1.50; extra == 'nebius'
@@ -269,6 +277,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'oci'
 Requires-Dist: alembic>=1.10.2; extra == 'oci'
 Requires-Dist: apscheduler<4; extra == 'oci'
 Requires-Dist: asyncpg; extra == 'oci'
+Requires-Dist: backports-entry-points-selectable; extra == 'oci'
 Requires-Dist: docker>=6.0.0; extra == 'oci'
 Requires-Dist: fastapi; extra == 'oci'
 Requires-Dist: grpcio>=1.50; extra == 'oci'
@@ -292,6 +301,7 @@ Requires-Dist: alembic-postgresql-enum; extra == 'server'
 Requires-Dist: alembic>=1.10.2; extra == 'server'
 Requires-Dist: apscheduler<4; extra == 'server'
 Requires-Dist: asyncpg; extra == 'server'
+Requires-Dist: backports-entry-points-selectable; extra == 'server'
 Requires-Dist: docker>=6.0.0; extra == 'server'
 Requires-Dist: fastapi; extra == 'server'
 Requires-Dist: grpcio>=1.50; extra == 'server'

dstack-0.19.7/docs/docs/concepts/plugins.md

@@ -0,0 +1,116 @@
+# Plugins
+
+The `dstack` plugin system allows extending `dstack` server functionality using external Python packages.
+
+!!! info "Experimental"
+    Plugins are currently an _experimental_ feature.
+    Backward compatibility is not guaranteed across releases.
+
+## Enable plugins
+
+To enable a plugin, list it under `plugins` in [`server/config.yml`](../reference/server/config.yml.md):
+
+<div editor-title="server/config.yml"> 
+
+```yaml
+plugins:
+  - my_dstack_plugin
+  - some_other_plugin
+projects:
+- name: main
+```
+
+</div>
+
+On the next server restart, you should see a log message indicating that the plugin is loaded.
+
+## Create plugins
+
+To create a plugin, create a Python package that implements a subclass of
+`dstack.plugins.Plugin` and exports this subclass as a "dstack.plugins" entry point.
+
+1. Init the plugin package:
+
+    <div class="termy">
+
+    ```shell
+    $ uv init --library
+    ```
+
+    </div>
+
+2. Define `ApplyPolicy` and `Plugin` subclasses:
+
+    <div editor-title="src/example_plugin/__init__.py"> 
+
+    ```python
+    from dstack.plugins import ApplyPolicy, Plugin, RunSpec, get_plugin_logger
+
+    logger = get_plugin_logger(__name__)
+
+    class ExamplePolicy(ApplyPolicy):
+        def on_run_apply(self, user: str, project: str, spec: RunSpec) -> RunSpec:
+            # ...
+            return spec
+    
+    class ExamplePlugin(Plugin):
+        
+        def get_apply_policies(self) -> list[ApplyPolicy]:
+            return [ExamplePolicy()]
+    ```
+
+    </div>
+
+3. Specify a "dstack.plugins" entry point in `pyproject.toml`:
+
+    <div editor-title="pyproject.toml"> 
+
+    ```toml
+    [project.entry-points."dstack.plugins"]
+    example_plugin = "example_plugin:ExamplePlugin"
+    ```
+
+    </div>
+
+Then you can install the plugin package into your Python environment and enable it via `server/config.yml`.
+
+??? info "Plugins in Docker"
+    If you deploy `dstack` using a Docker image you can add plugins either
+    by including them in your custom image built upon the `dstack` server image,
+    or by mounting installed plugins as volumes.
+
+## Apply policies
+
+Currently the only plugin functionality is apply policies.
+Apply policies allow modifying specs of runs, fleets, volumes, and gateways submitted on `dstack apply`.
+Subclass `dstack.plugins.ApplyPolicy` to implement them.
+
+Here's an example of how to enforce certain rules using apply policies:
+
+<div editor-title="src/example_plugin/__init__.py"> 
+
+```python
+class ExamplePolicy(ApplyPolicy):
+    def on_run_apply(self, user: str, project: str, spec: RunSpec) -> RunSpec:
+        # Forcing some limits
+        spec.configuration.max_price = 2.0
+        spec.configuration.max_duration = "1d"
+        # Setting some extra tags
+        if spec.configuration.tags is None:
+            spec.configuration.tags = {}
+        spec.configuration.tags |= {
+            "team": "my_team",
+        }
+        # Forbid something
+        if spec.configuration.privileged:
+            logger.warning("User %s tries to run privileged containers", user)
+            raise ValueError("Running privileged containers is forbidden")
+        # Set some service-specific properties
+        if isinstance(spec.configuration, Service):  
+            spec.configuration.https = True
+        return spec
+```
+
+</div>
+
+For more information on the plugin development, see the [plugin example](https://github.com/dstackai/dstack/tree/master/examples/plugins/example_plugin).

dstack-0.19.7/examples/plugins/example_plugin/.python-version

@@ -0,0 +1 @@
+3.11

dstack-0.19.7/examples/plugins/example_plugin/README.md

@@ -0,0 +1,52 @@
+## Overview
+
+This is a basic `dstack` plugin example.
+You can use it as a reference point when implementing new `dstack` plugins.
+
+## Steps
+
+1. Init the plugin package:
+
+    ```
+    uv init --library
+    ```
+
+2. Define `ApplyPolicy` and `Plugin` subclasses:
+
+    ```python
+    from dstack.plugins import ApplyPolicy, Plugin, RunSpec, get_plugin_logger
+
+
+    logger = get_plugin_logger(__name__)
+
+
+    class ExamplePolicy(ApplyPolicy):
+
+        def on_run_apply(self, user: str, project: str, spec: RunSpec) -> RunSpec:
+            # ...
+            return spec
+
+
+    class ExamplePlugin(Plugin):
+        
+        def get_apply_policies(self) -> list[ApplyPolicy]:
+            return [ExamplePolicy()]
+
+    ```
+
+3. Specify a "dstack.plugins" entry point in `pyproject.toml`:
+
+    ```toml
+    [project.entry-points."dstack.plugins"]
+    example_plugin = "example_plugin:ExamplePlugin"
+    ```
+
+4. Make sure to install the plugin and enable it in the `server/config.yml`:
+
+    ```yaml
+    plugins:
+    - example_plugin
+    projects:
+    - name: main
+      # ...
+    ```

dstack-0.19.7/examples/plugins/example_plugin/pyproject.toml

@@ -0,0 +1,17 @@
+[project]
+name = "example-plugin"
+version = "0.1.0"
+description = "A dstack plugin example"
+readme = "README.md"
+authors = [
+    { name = "Victor Skvortsov", email = "victor@dstack.ai" }
+]
+requires-python = ">=3.9"
+dependencies = []
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project.entry-points."dstack.plugins"]
+example_plugin = "example_plugin:ExamplePlugin"

dstack-0.19.7/examples/plugins/example_plugin/src/example_plugin/__init__.py

@@ -0,0 +1,34 @@
+from dstack.api import Service
+from dstack.plugins import ApplyPolicy, GatewaySpec, Plugin, RunSpec, get_plugin_logger
+
+logger = get_plugin_logger(__name__)
+
+
+class ExamplePolicy(ApplyPolicy):
+    def on_run_apply(self, user: str, project: str, spec: RunSpec) -> RunSpec:
+        # Forcing some limits
+        spec.configuration.max_price = 2.0
+        spec.configuration.max_duration = "1d"
+        # Setting some extra tags
+        if spec.configuration.tags is None:
+            spec.configuration.tags = {}
+        spec.configuration.tags |= {
+            "team": "my_team",
+        }
+        # Forbid something
+        if spec.configuration.privileged:
+            logger.warning("User %s tries to run privileged containers", user)
+            raise ValueError("Running privileged containers is forbidden")
+        # Set some service-specific properties
+        if isinstance(spec.configuration, Service):
+            spec.configuration.https = True
+        return spec
+
+    def on_gateway_apply(self, user: str, project: str, spec: GatewaySpec) -> GatewaySpec:
+        # Forbid creating new gateways altogether
+        raise ValueError("Creating gateways is forbidden")
+
+
+class ExamplePlugin(Plugin):
+    def get_apply_policies(self) -> list[ApplyPolicy]:
+        return [ExamplePolicy()]

{dstack-0.19.6rc1 → dstack-0.19.7}/mkdocs.yml

@@ -206,6 +206,7 @@ nav:
           - Backends: docs/concepts/backends.md
           - Projects: docs/concepts/projects.md
           - Gateways: docs/concepts/gateways.md
+          - Plugins: docs/concepts/plugins.md
       - Guides:
           - Protips: docs/guides/protips.md
           - Server deployment: docs/guides/server-deployment.md

{dstack-0.19.6rc1 → dstack-0.19.7}/pyproject.toml

@@ -32,7 +32,7 @@ dependencies = [
     "python-multipart>=0.0.16",
     "filelock",
     "psutil",
-    "gpuhunt>=0.1.3,<0.2.0",
+    "gpuhunt==0.1.5",
     "argcomplete>=3.5.0",
 ]
 
@@ -125,6 +125,7 @@ server = [
     "python-json-logger>=3.1.0",
     "prometheus-client",
     "grpcio>=1.50",
+    "backports.entry-points-selectable",
 ]
 aws = [
     "boto3",

dstack-0.19.7/runner/.justfile

@@ -0,0 +1,110 @@
+# Justfile for building and uploading dstack runner and shim
+#
+# Run `just` to see all available commands
+#
+# Configuration:
+# - DSTACK_SHIM_UPLOAD_VERSION: Version of the runner and shim to upload
+# - DSTACK_SHIM_UPLOAD_S3_BUCKET: S3 bucket to upload binaries to
+#
+# Build Process:
+# - Runner is always built for linux/amd64
+# - Shim can be built for any platform (defaults to host platform)
+# - When uploading, shim is automatically built for linux/amd64
+#
+# Development Workflows:
+# - Local Development:
+#   * Use build recipes to build binaries for local testing
+#   * See README.md for instructions on running dstack server with local binaries
+#   * No need to upload binaries for local development
+#
+# - Remote Development:
+#   * Use upload recipes to build and upload binaries to S3
+#   * See README.md for instructions on running dstack server with uploaded binaries
+#   * Upload is required for testing with standard backends (including SSH fleets)
+
+default:
+    @just --list
+
+# Version of the runner and shim to upload
+export version := env_var("DSTACK_SHIM_UPLOAD_VERSION")
+
+# S3 bucket to upload binaries to
+export s3_bucket := env_var("DSTACK_SHIM_UPLOAD_S3_BUCKET")
+
+# Download URLs
+export runner_download_url := "s3://" + s3_bucket + "/" + version + "/binaries/dstack-runner-linux-amd64"
+export shim_download_url := "s3://" + s3_bucket + "/" + version + "/binaries/dstack-shim-linux-amd64"
+
+# Shim build configuration
+export shim_os := ""
+export shim_arch := ""
+
+# Build runner
+[private]
+build-runner-binary:
+    #!/usr/bin/env bash
+    set -e
+    echo "Building runner for linux/amd64"
+    cd {{source_directory()}}/cmd/runner && GOOS=linux GOARCH=amd64 go build
+    echo "Runner build complete!"
+
+# Build shim
+[private]
+build-shim-binary:
+    #!/usr/bin/env bash
+    set -e
+    cd {{source_directory()}}/cmd/shim
+    if [ -n "$shim_os" ] && [ -n "$shim_arch" ]; then
+        echo "Building shim for $shim_os/$shim_arch"
+        GOOS=$shim_os GOARCH=$shim_arch go build
+    else
+        echo "Building shim for current platform"
+        go build
+    fi
+    echo "Shim build complete!"
+
+# Build both runner and shim
+build-runner: build-runner-binary build-shim-binary
+    echo "Build complete! Linux AMD64 binaries are in their respective cmd directories."
+
+# Clean build artifacts
+clean-runner:
+    rm -f {{source_directory()}}/cmd/runner/runner
+    rm -f {{source_directory()}}/cmd/shim/shim
+    echo "Build artifacts cleaned!"
+
+# Run tests for runner and shim
+test-runner:
+    cd {{source_directory()}} && go test -v ./...
+
+# Validate shim is built for linux/amd64
+[private]
+validate-shim-binary:
+    #!/usr/bin/env bash
+    set -e
+    if ! file {{source_directory()}}/cmd/shim/shim | grep -q "ELF 64-bit LSB executable, x86-64"; then
+        echo "Error: Shim must be built for linux/amd64 for upload"
+        exit 1
+    fi
+
+# Upload both runner and shim to S3
+upload-runner: upload-runner-binary upload-shim-binary
+
+# Upload runner to S3
+[private]
+upload-runner-binary:
+    #!/usr/bin/env bash
+    set -e
+    just build-runner-binary
+    aws s3 cp {{source_directory()}}/cmd/runner/runner "{{runner_download_url}}" --acl public-read
+    echo "Uploaded runner to S3"
+
+# Upload shim to S3
+[private]
+upload-shim-binary:
+    #!/usr/bin/env bash
+    set -e
+    just --set shim_os linux --set shim_arch amd64 build-shim-binary
+    just validate-shim-binary
+    aws s3 cp {{source_directory()}}/cmd/shim/shim "{{shim_download_url}}" --acl public-read
+    echo "Uploaded shim to S3"

{dstack-0.19.6rc1 → dstack-0.19.7}/runner/README.md

@@ -2,7 +2,7 @@
 
 For overview of `dstack-shim` and `dstack-runner`, see [/contributing/RUNNER-AND-SHIM.md](../contributing/RUNNER-AND-SHIM.md).
 
-## Development
+## Running locally
 
 Here's the steps to build `dstack-shim` and `dstack-runner` and run `dstack` with them locally:
 
@@ -40,6 +40,8 @@ Now you can call shim API:
 >>> s.submit("","", "ubuntu", None)
 ```
 
+### Local backend
+
 You can also run `dstack` end-to-end with local shim and runner by enabling the `local` backend on dstack server:
 
 ```shell
@@ -76,6 +78,38 @@ The `local` backend will submit the run to the locally started shim and runner.
 Continue? [y/n]:
 ```
 
+## Testing remotely
+
+You can also test the built shim and runner using standard backends (including SSH fleets).
+
+> [!NOTE]
+> To run with standard backends, both the runner and shim must be built for linux/amd64.
+
+Build the runner and shim, and upload them to S3 automatically using `just` (see [`justfile`](justfile)).
+
+> [!IMPORTANT]
+> Before running any `just` commands that upload to S3, you must set the following environment variables:
+>
+> ```shell
+> export DSTACK_SHIM_UPLOAD_VERSION="your-version"
+> export DSTACK_SHIM_UPLOAD_S3_BUCKET="your-bucket"
+> ```
+>
+> These variables are required and must be set before running any upload commands.
+
+```shell
+just upload
+```
+
+To use the built shim and runner with the dstack server, pass the URLs via `DSTACK_SHIM_DOWNLOAD_URL` and `DSTACK_RUNNER_DOWNLOAD_URL`:
+
+```shell
+export DSTACK_SHIM_DOWNLOAD_URL="https://${DSTACK_SHIM_UPLOAD_S3_BUCKET}.s3.amazonaws.com/${DSTACK_SHIM_UPLOAD_VERSION}/binaries/dstack-shim-linux-amd64"
+export DSTACK_RUNNER_DOWNLOAD_URL="https://${DSTACK_SHIM_UPLOAD_S3_BUCKET}.s3.amazonaws.com/${DSTACK_SHIM_UPLOAD_VERSION}/binaries/dstack-runner-linux-amd64"
+
+dstack server --log-level=debug
+```
+
 ## Dependencies (WIP)
 
 These are nonexhaustive lists of external dependencies (executables, libraries) of the `dstack-*` binaries.

{dstack-0.19.6rc1 → dstack-0.19.7}/runner/internal/shim/docker.go

@@ -151,6 +151,14 @@ func (d *DockerRunner) restoreStateFromContainers(ctx context.Context) error {
 						gpuIDs = append(gpuIDs, device.PathOnHost)
 					}
 				}
+			case host.GpuVendorTenstorrent:
+				for _, device := range containerFull.HostConfig.Resources.Devices {
+					if strings.HasPrefix(device.PathOnHost, "/dev/tenstorrent/") {
+						// Extract the device ID from the path
+						deviceID := strings.TrimPrefix(device.PathOnHost, "/dev/tenstorrent/")
+						gpuIDs = append(gpuIDs, deviceID)
+					}
+				}
 			case host.GpuVendorIntel:
 				for _, envVar := range containerFull.Config.Env {
 					if indices, found := strings.CutPrefix(envVar, "HABANA_VISIBLE_DEVICES="); found {
@@ -564,8 +572,9 @@ func formatAndMountVolume(ctx context.Context, volume VolumeInfo) error {
 }
 
 func getVolumeMountPoint(volumeName string) string {
-	// Put volumes in data-specific dir to avoid clashes with host dirs
-	return fmt.Sprintf("/dstack-volumes/%s", volumeName)
+	// Put volumes in dstack-specific dir to avoid clashes with host dirs.
+	// /mnt/disks is used since on some VM images other places may not be writable (e.g. GCP COS).
+	return fmt.Sprintf("/mnt/disks/dstack-volumes/%s", volumeName)
 }
 
 func prepareInstanceMountPoints(taskConfig TaskConfig) error {
@@ -1008,6 +1017,7 @@ func configureGpuDevices(hostConfig *container.HostConfig, gpuDevices []GPUDevic
 func configureGpus(config *container.Config, hostConfig *container.HostConfig, vendor host.GpuVendor, ids []string) {
 	// NVIDIA: ids are identifiers reported by nvidia-smi, GPU-<UUID> strings
 	// AMD: ids are DRI render node paths, e.g., /dev/dri/renderD128
+	// Tenstorrent: ids are device indices to be used with /dev/tenstorrent/<id>
 	switch vendor {
 	case host.GpuVendorNvidia:
 		hostConfig.Resources.DeviceRequests = append(
@@ -1050,6 +1060,27 @@ func configureGpus(config *container.Config, hostConfig *container.HostConfig, v
 		// --security-opt=seccomp=unconfined
 		hostConfig.SecurityOpt = append(hostConfig.SecurityOpt, "seccomp=unconfined")
 		// TODO: in addition, for non-root user, --group-add=video, and possibly --group-add=render, are required.
+	case host.GpuVendorTenstorrent:
+		// For Tenstorrent, simply add each device
+		for _, id := range ids {
+			devicePath := fmt.Sprintf("/dev/tenstorrent/%s", id)
+			hostConfig.Resources.Devices = append(
+				hostConfig.Resources.Devices,
+				container.DeviceMapping{
+					PathOnHost:        devicePath,
+					PathInContainer:   devicePath,
+					CgroupPermissions: "rwm",
+				},
+			)
+		}
+		// Check and mount hugepages-1G if it exists
+		if _, err := os.Stat("/dev/hugepages-1G"); err == nil {
+			hostConfig.Mounts = append(hostConfig.Mounts, mount.Mount{
+				Type:   mount.TypeBind,
+				Source: "/dev/hugepages-1G",
+				Target: "/dev/hugepages-1G",
+			})
+		}
 	case host.GpuVendorIntel:
 		// All options are listed here:
 		// https://docs.habana.ai/en/latest/Installation_Guide/Additional_Installation/Docker_Installation.html