Add another cause for 401 Unauthorized error #1812
Open
+26
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@microsoft-github-policy-service agree |
|
@jkyamog : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 8c82ce8: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have identified an additional scenario that can cause a 401 Unauthorized error, distinct from the existing Cause 1: 401 Unauthorized error. This new scenario occurs due to an architecture mismatch between the container image in Azure Container Registry (ACR) and the node architecture (for example, arm64 vs. amd64) in Azure Kubernetes Service (AKS). Additionally, the current troubleshooting steps provided in the documentation do not resolve this issue and instead result in an unexpected "exec format error."
This PR adds this new cause and its corresponding solution to the documentation.
#sign-off