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.