Skip to content

Commit 51156fe

Browse files
committed
Azure Container offers certification
1 parent 8398a5a commit 51156fe

File tree

2 files changed

+46
-0
lines changed

2 files changed

+46
-0
lines changed

articles/marketplace/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -209,6 +209,8 @@
209209
href: azure-container-plan-availability.md
210210
- name: Plan technical configuration
211211
href: azure-container-plan-technical-configuration.md
212+
- name: Container certification troubleshooting
213+
href: azure-container-certification-faq.yml
212214
- name: Azure virtual machine offer
213215
items:
214216
- name: Plan the offer
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
### YamlMime:FAQ
2+
metadata:
3+
title: Container certification troubleshooting for Azure Marketplace
4+
description: Troubleshoot common issues related to testing and certifying container products for Azure Marketplace.
5+
ms.service: marketplace
6+
ms.subservice: partnercenter-marketplace-publisher
7+
ms.topic: faq
8+
author: mathapli
9+
ms.author: mathapli
10+
ms.date: 09/27/2021
11+
title: Troubleshoot container certification
12+
summary: |
13+
When you publish your container products to Azure Marketplace, the Azure team validates it to ensure that it's secure. If your container products fails any of the tests, it won't be published. You'll receive an error message that describes the issue.
14+
15+
This article explains common error messages during container publishing, along with related solutions.
16+
17+
> [!NOTE]
18+
> If you have questions about this article or suggestions for improvement, contact [Partner Center support](https://go.microsoft.com/fwlink/?linkid=2165533).
19+
20+
21+
sections:
22+
- name: Ignored
23+
questions:
24+
- question: |
25+
Vulnerability failure
26+
answer: |
27+
A vulnerability is an exploitable risk and/or an unsecured entry points that can be used by malicious actors for nefarious actions.
28+
If you are planning to publish container products, you should scan your product for vulnerability and fix them before publishing the container product.
29+
If your existing container products have vulnerabilities in them, you should deprecate/hide the affected offer and republish after fixing the vulnerabilities.
30+
31+
- question: |
32+
Malware failure
33+
answer: |
34+
A malware, or malicious software, is a file or program that is designed to be harmful to computer, network or servers.
35+
If you are planning to publish container products, you should scan your product for malware, identify all files which contain malware and remove them before publishing the container product.
36+
If your existing container products have malware, you should deprecate/hide the affected offers and republish the patched product.
37+
38+
39+
additionalContent: |
40+
41+
## Next steps
42+
- [Plan an Azure container offer](marketplace-containers.md)
43+
- [Active marketplace rewards](marketplace-rewards.md)
44+
- If you have questions or feedback for improvement, contact [Partner Center support](https://go.microsoft.com/fwlink/?linkid=2165533)

0 commit comments

Comments
 (0)