Azure / Azure/azure-rest-api-specs

Container Instances - No support for fileshares with AES-256-GCM

Open
#42,307 0 comments 0 reactions 0 assignees View on GitHub
customer-reported question
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

Currently if you mount a fileshare to Azure Container Instances from a storage account, wich is using AES-256-GCM
The container is stuck in a waiting state, without additional information.

2 issues:

1. The user doesn't know the root cause, and I still don't know if this is, since my support engineer can't provide details.
2. AES-256-GCM is required for CIS compliance: https://support.icompaas.com/support/solutions/articles/62000234038-ensure-smb-channel-encryption-is-set-to-aes-256-gcm-or-higher-for-smb-file-shares-automated-

My friendly azure support engineer suggested I create a ticket here.

Contributor guide

Open the contributing guide

Research direction

No file, test, or entry point is identified in the issue. Start by reproducing the Azure Container Instances fileshare mount with AES-256-GCM and determine whether the failure belongs in these REST API specifications; done requires a confirmed support or diagnostic change with a clear way to verify it.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
api, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.