skypilot-org/skypilot

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

Open

#8,504 opened on 2026年1月7日

GitHub で見る
 (5 comments) (0 reactions) (0 assignees)Python (4,859 stars) (311 forks)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
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-3 hours
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.