skypilot-org/skypilot

New Azure cloud bucket (container) created in different region from cluster

Open

#8,504 建立於 2026年1月7日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)Python (4,859 star) (311 fork)batch import
good first issuegood starter issues

描述

With skypilot 0.11.1 The following minimal config creates a VM in azure/westus2, but surprisingly creates a bucket/"container" in eastus with "Geo-redundant storage (GRS)" in westus.

I expected that the default would be to create the bucket in the same region as the VM for efficiency and reduced transfer costs, perhaps using just the Locally-redundant storage (LRS) option.

resources:
  infra: azure/westus2
  autostop:
    idle_minutes: 10
    down: false  # just stop don't delete.

file_mounts:
  /outputs:
    name: dshydro-skypilot-output
    store: azure
    persistent: True
    mode: MOUNT_CACHED

Our current workaround is to create the bucket in advance through other means...

貢獻者指南

技術棧
pythonazure
領域
cloudbackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonAzure accountSkyPilot basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Investigate the cloud storage creation logic in SkyPilot, specifically the Azure storage account creation code. Check if the region for the storage account is defaulting to eastus instead of using the cluster region. Look at the file mount configuration parsing and how the 'store' parameter is handled for Azure. The issue mentions that the bucket is created in eastus with GRS; the expected behavior is to use the same region as the VM and LRS. A fix would involve modifying the region selection for storage accounts to match the cluster region.