skypilot-org/skypilot

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

Open

#8504 opened on Jan 7, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Python (4,859 stars) (311 forks)batch import
good first issuegood starter issues

Description

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...

Contributor guide

Tech stack
pythonazure
Domain
cloudbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonAzure accountSkyPilot basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.