diff --git a/docs/swr/umn/.placeholder b/docs/swr/umn/.placeholder
deleted file mode 100644
index e69de29b..00000000
diff --git a/docs/swr/umn/ALL_META.TXT.json b/docs/swr/umn/ALL_META.TXT.json
index 26e0993a..d8622857 100644
--- a/docs/swr/umn/ALL_META.TXT.json
+++ b/docs/swr/umn/ALL_META.TXT.json
@@ -1,311 +1,715 @@
[
{
"uri":"swr_pd_index.html",
+ "node_id":"swr_pd_index.xml",
"product_code":"swr",
"code":"1",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Service Overview",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Service Overview",
"githuburl":""
},
{
"uri":"swr_03_0001.html",
+ "node_id":"swr_03_0001.xml",
"product_code":"swr",
"code":"2",
"des":"SoftWare Repository for Container (SWR) allows you to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applicatio",
"doc_type":"usermanual",
- "kw":"Introduction,Service Overview,User Guide",
+ "kw":"Introduction,Service Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Introduction",
"githuburl":""
},
{
"uri":"swr_03_0002.html",
+ "node_id":"swr_03_0002.xml",
"product_code":"swr",
"code":"3",
"des":"You can directly push and pull container images without platform build or O&M.SWR provides an easy-to-use management console for full lifecycle management over container ",
"doc_type":"usermanual",
- "kw":"Advantages,Service Overview,User Guide",
+ "kw":"Advantages,Service Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Advantages",
"githuburl":""
},
{
"uri":"swr_03_0004.html",
+ "node_id":"swr_03_0004.xml",
"product_code":"swr",
"code":"4",
- "des":"You can use SWR to build, push, pull, synchronize, and delete container images.AdvantagesP2P download acceleration ensures faster image pull for CCE clusters.Up to 99.999",
+ "des":"You can use SWR to build, push, pull, synchronize, and delete container images.AdvantagesPull acceleration ensures faster image pull for CCE clusters.Up to 99.999999999% ",
"doc_type":"usermanual",
- "kw":"Application Scenarios,Service Overview,User Guide",
+ "kw":"Application Scenarios,Service Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Application Scenarios",
"githuburl":""
},
{
"uri":"swr_03_0003.html",
+ "node_id":"swr_03_0003.xml",
"product_code":"swr",
"code":"5",
"des":"Images are like templates that include everything needed to run applications. When deploying containerized applications, you can use images from the Docker image center a",
"doc_type":"usermanual",
- "kw":"Basic Concepts,Service Overview,User Guide",
+ "kw":"Basic Concepts,Service Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Basic Concepts",
"githuburl":""
},
{
"uri":"swr_03_0007.html",
+ "node_id":"swr_03_0007.xml",
"product_code":"swr",
"code":"6",
"des":"Quotas are imposed on the number of organizations a user can create. Table 1 lists the quotas imposed by SWR.",
"doc_type":"usermanual",
- "kw":"Notes and Constraints,Service Overview,User Guide",
+ "kw":"Notes and Constraints,Service Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Notes and Constraints",
"githuburl":""
},
{
- "uri":"swr_03_0006.html",
- "product_code":"swr",
+ "uri":"en-us_topic_0000001488156484.html",
+ "node_id":"en-us_topic_0000001488156484.xml",
+ "product_code":"",
"code":"7",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Permissions",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Permissions",
+ "githuburl":""
+ },
+ {
+ "uri":"en-us_topic_0000001488156664.html",
+ "node_id":"en-us_topic_0000001488156664.xml",
+ "product_code":"",
+ "code":"8",
+ "des":"By default, new IAM users do not have any permissions granted. You need to add them to one or more groups and attach permissions policies or roles to these groups. In thi",
+ "doc_type":"",
+ "kw":"SWR Permissions,Permissions,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"SWR Permissions",
+ "githuburl":""
+ },
+ {
+ "uri":"swr_03_0006.html",
+ "node_id":"swr_03_0006.xml",
+ "product_code":"swr",
+ "code":"9",
"des":"SWR works with other cloud services and requires permissions to access them. For details, see Figure 1.Cloud Container Engine (CCE)CCE is a high-performance, high-reliabi",
"doc_type":"usermanual",
- "kw":"Related Services,Service Overview,User Guide",
+ "kw":"Related Services,Service Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Related Services",
"githuburl":""
},
{
"uri":"swr_01_0009.html",
+ "node_id":"swr_01_0009.xml",
"product_code":"swr",
- "code":"8",
+ "code":"10",
"des":"SoftWare Repository for Container (SWR) allows you to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applicatio",
"doc_type":"usermanual",
- "kw":"Introduction,User Guide",
- "title":"Introduction",
+ "kw":"Overview,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Overview",
+ "githuburl":""
+ },
+ {
+ "uri":"swr_01_0070.html",
+ "node_id":"swr_01_0070.xml",
+ "product_code":"swr",
+ "code":"11",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"usermanual",
+ "kw":"Permissions Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Permissions Management",
+ "githuburl":""
+ },
+ {
+ "uri":"swr_01_0072.html",
+ "node_id":"swr_01_0072.xml",
+ "product_code":"swr",
+ "code":"12",
+ "des":"This section describes how to use IAM for fine-grained permission management on your SWR resources. With IAM, you can:Create IAM users for employees based on your enterpr",
+ "doc_type":"usermanual",
+ "kw":"Creating a User and Granting SWR Permissions,Permissions Management,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Creating a User and Granting SWR Permissions",
"githuburl":""
},
{
"uri":"swr_01_0006.html",
+ "node_id":"swr_01_0006.xml",
"product_code":"swr",
- "code":"9",
+ "code":"13",
"des":"The container engine, namely, Docker, is an open-source engine which allows you to create a lightweight, portable, and self-sufficient container for any application. SWR ",
"doc_type":"usermanual",
"kw":"Dockerfile,Nginx image,Nginx image,Edit Dockerfile,.tar,.tar.gz,Basics of the Container Engine,User ",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Basics of the Container Engine",
"githuburl":""
},
{
"uri":"swr_01_0028.html",
+ "node_id":"swr_01_0028.xml",
"product_code":"swr",
- "code":"10",
+ "code":"14",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Image Management",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Image Management",
"githuburl":""
},
{
"uri":"swr_01_0011.html",
+ "node_id":"swr_01_0011.xml",
"product_code":"swr",
- "code":"11",
+ "code":"15",
"des":"This section walks you through the steps of uploading an image to SWR through the client by taking the nginx:v1 image built in Basics of the Container Engine as an exampl",
"doc_type":"usermanual",
- "kw":"Push the image to the image repository,Uploading an Image Through the Client,Image Management,User G",
+ "kw":"Push the image to the image repository,Uploading an Image Through the Client,Image Management,User M",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Uploading an Image Through the Client",
"githuburl":""
},
{
"uri":"swr_01_1000.html",
+ "node_id":"swr_01_1000.xml",
"product_code":"swr",
- "code":"12",
+ "code":"16",
"des":"This section describes how to obtain a login command that is valid for a year.For security purposes, it is advised to obtain the login command in the development environm",
"doc_type":"usermanual",
- "kw":"obtain the login key,Obtaining a Long-Term Valid Login Command,Image Management,User Guide",
+ "kw":"obtain the login key,Obtaining a Long-Term Valid Login Command,Image Management,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Obtaining a Long-Term Valid Login Command",
"githuburl":""
},
{
"uri":"swr_01_0017.html",
+ "node_id":"swr_01_0017.xml",
"product_code":"swr",
- "code":"13",
+ "code":"17",
"des":"You can run the docker pull command to pull images from SWR.Run the docker images command to check whether the images are successfully pulled.docker save [Image name:tag ",
"doc_type":"usermanual",
- "kw":"Pulling an Image,Image Management,User Guide",
+ "kw":"Pulling an Image,Image Management,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Pulling an Image",
"githuburl":""
},
{
"uri":"swr_01_0016.html",
+ "node_id":"swr_01_0016.xml",
"product_code":"swr",
- "code":"14",
+ "code":"18",
"des":"After uploading an image, you can set image attributes, including its type (private by default), category and description.Public images can be pulled by all users; wherea",
"doc_type":"usermanual",
"kw":"set image attributes,type (private by default), category and description,Setting Image Attributes,Im",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Setting Image Attributes",
"githuburl":""
},
{
"uri":"swr_01_0026.html",
+ "node_id":"swr_01_0026.xml",
"product_code":"swr",
- "code":"15",
+ "code":"19",
"des":"You can share your private images with other users and grant the users access permissions.The user with whom you shared the image can then log in to SWR console to view t",
"doc_type":"usermanual",
- "kw":"Sharing Private Images,Image Management,User Guide",
+ "kw":"Sharing Private Images,Image Management,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Sharing Private Images",
"githuburl":""
},
{
"uri":"swr_01_0014.html",
+ "node_id":"swr_01_0014.xml",
"product_code":"swr",
- "code":"16",
+ "code":"20",
"des":"Organizations enable efficient management of images. Organizations are used to isolate image repositories. With each organization being limited to one company or departme",
"doc_type":"usermanual",
- "kw":"Organization Management,User Guide",
+ "kw":"Organization Management,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Organization Management",
"githuburl":""
},
{
"uri":"swr_01_0015.html",
+ "node_id":"swr_01_0015.xml",
"product_code":"swr",
- "code":"17",
- "des":"To manage SWR permissions, you can use Identity and Access Management (IAM). If you have the SWR Admin or Tenant Administrator permission, you become an admin user of SWR",
+ "code":"21",
+ "des":"To manage SWR permissions, you can use Identity and Access Management (IAM). If you have the SWR Administrator or Tenant Administrator permission, you become an admin use",
"doc_type":"usermanual",
- "kw":"Read,Write,Manage,Permission,Permission,User Permissions,User Guide",
+ "kw":"Read,Write,Manage,Permission,Permission,User Permissions,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"User Permissions",
"githuburl":""
},
{
"uri":"swr_faq_index.html",
+ "node_id":"swr_faq_index.xml",
"product_code":"swr",
- "code":"18",
+ "code":"22",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"FAQs",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"FAQs",
"githuburl":""
},
{
"uri":"swr_faq_1001.html",
+ "node_id":"swr_faq_1001.xml",
"product_code":"swr",
- "code":"19",
+ "code":"23",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"General FAQs",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"General FAQs",
"githuburl":""
},
{
- "uri":"swr_faq_0013.html",
+ "uri":"swr_faq_1011.html",
+ "node_id":"swr_faq_1011.xml",
"product_code":"swr",
- "code":"20",
- "des":"SWR has no limit on the number of images. You can upload any number of images.SWR has no restriction on the kernel architecture of images. There is no difference between ",
+ "code":"24",
+ "des":"SoftWare Repository for Container (SWR) allows users to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applicat",
"doc_type":"usermanual",
- "kw":"SWR Overview,General FAQs,User Guide",
- "title":"SWR Overview",
+ "kw":"What Is SWR?,General FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"What Is SWR?",
+ "githuburl":""
+ },
+ {
+ "uri":"swr_faq_0013.html",
+ "node_id":"swr_faq_0013.xml",
+ "product_code":"swr",
+ "code":"25",
+ "des":"SWR has no limit on the number of images. You can upload any number of images.The bandwidth of SWR dynamically changes based on actual usage.The billing items of SWR incl",
+ "doc_type":"usermanual",
+ "kw":"About SWR,General FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"About SWR",
"githuburl":""
},
{
"uri":"swr_faq_0012.html",
+ "node_id":"swr_faq_0012.xml",
"product_code":"swr",
- "code":"21",
+ "code":"26",
"des":"The following two approaches are for you to consider. Approach 1 is for images that will only be updated occasionally whereas approach 2 is for images that will be freque",
"doc_type":"usermanual",
- "kw":"How Do I Create a Container Image?,General FAQs,User Guide",
+ "kw":"How Do I Create a Container Image?,General FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"How Do I Create a Container Image?",
"githuburl":""
},
{
"uri":"swr_faq_0004.html",
+ "node_id":"swr_faq_0004.xml",
"product_code":"swr",
- "code":"22",
+ "code":"27",
"des":"Run the docker save command to compress the container image into a .tar or .tar.gz package. The command format is as follows:docker save [OPTIONS] IMAGE [IMAGE...][OPTION",
"doc_type":"usermanual",
- "kw":"How Do I Create an Image Package?,General FAQs,User Guide",
+ "kw":"How Do I Create an Image Package?,General FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"How Do I Create an Image Package?",
"githuburl":""
},
+ {
+ "uri":"en-us_topic_0000001539549873.html",
+ "node_id":"en-us_topic_0000001539549873.xml",
+ "product_code":"",
+ "code":"28",
+ "des":"No quotas are imposed on SWR images. You can push as many images as you need.Quotas are imposed on the number of organizations a user can create, as shown in Table 1.",
+ "doc_type":"",
+ "kw":"Are There Quotas for SWR Resources?,General FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Are There Quotas for SWR Resources?",
+ "githuburl":""
+ },
+ {
+ "uri":"en-us_topic_0000001488470084.html",
+ "node_id":"en-us_topic_0000001488470084.xml",
+ "product_code":"",
+ "code":"29",
+ "des":"Symptom: The creation of an organization fails, and a message is displayed indicating that the organization already exists. However, the organization is not found on the ",
+ "doc_type":"",
+ "kw":"Why Does Organization Creation Fail?,General FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Why Does Organization Creation Fail?",
+ "githuburl":""
+ },
{
"uri":"swr_faq_1002.html",
+ "node_id":"swr_faq_1002.xml",
"product_code":"swr",
- "code":"23",
+ "code":"30",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Image Management FAQs",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Image Management FAQs",
"githuburl":""
},
{
- "uri":"swr_faq_0015.html",
+ "uri":"swr_faq_1012.html",
+ "node_id":"swr_faq_1012.xml",
"product_code":"swr",
- "code":"24",
+ "code":"31",
+ "des":"Currently, SWR does not provide APIs for image push. You can push images using the docker push command on a client or using the SWR console.Currently, SWR does not provid",
+ "doc_type":"usermanual",
+ "kw":"Image Push and Pull,Image Management FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"Image Push and Pull",
+ "githuburl":""
+ },
+ {
+ "uri":"swr_faq_1013.html",
+ "node_id":"swr_faq_1013.xml",
+ "product_code":"swr",
+ "code":"32",
+ "des":"500",
+ "doc_type":"usermanual",
+ "kw":"How Many Tenants Can I Share an SWR Private Image with?,Image Management FAQs,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
+ "title":"How Many Tenants Can I Share an SWR Private Image with?",
+ "githuburl":""
+ },
+ {
+ "uri":"swr_faq_0015.html",
+ "node_id":"swr_faq_0015.xml",
+ "product_code":"swr",
+ "code":"33",
"des":"Temporary login commands will expire after 24 hours.Long-term valid login commands are valid for a year.After you obtain a long-term valid login command, your temporary l",
"doc_type":"usermanual",
"kw":"What Are the Differences Between Long-Term Valid Login Commands and Temporary Login Commands?,Image ",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"What Are the Differences Between Long-Term Valid Login Commands and Temporary Login Commands?",
"githuburl":""
},
- {
- "uri":"swr_faq_0005.html",
- "product_code":"swr",
- "code":"25",
- "des":"Assume that a nginx image of v2.0.0 is created on the local Docker client. The docker images command is run to query SIZE of the image. The size is 22.8 MB.Run the docker",
- "doc_type":"usermanual",
- "kw":"Why Is an Image Uploaded Through the Client to SWR Different in Size From One Uploaded Through the S",
- "title":"Why Is an Image Uploaded Through the Client to SWR Different in Size From One Uploaded Through the SWR Console?",
- "githuburl":""
- },
- {
- "uri":"swr_faq_0035.html",
- "product_code":"swr",
- "code":"26",
- "des":"Container images stored in SWR cannot be directly downloaded through the console. You can perform the following operations to pull the images:Obtain the image pull comman",
- "doc_type":"usermanual",
- "kw":"Can I Pull Container Images on the SWR Console to a Local PC?,Image Management FAQs,User Guide",
- "title":"Can I Pull Container Images on the SWR Console to a Local PC?",
- "githuburl":""
- },
{
"uri":"swr_faq_2000.html",
+ "node_id":"swr_faq_2000.xml",
"product_code":"swr",
- "code":"27",
+ "code":"34",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
"kw":"Troubleshooting",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Troubleshooting",
"githuburl":""
},
{
"uri":"swr_faq_0016.html",
+ "node_id":"swr_faq_0016.xml",
"product_code":"swr",
- "code":"28",
+ "code":"35",
"des":"Possible causes are as follows:The container engine is not properly installed, in which case the following error is reported:docker: command not foundSolution: Reinstall ",
"doc_type":"usermanual",
- "kw":"Why Does the Login Command Fail to Be Executed?,Troubleshooting,User Guide",
+ "kw":"Why Does the Login Command Fail to Be Executed?,Troubleshooting,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Why Does the Login Command Fail to Be Executed?",
"githuburl":""
},
{
"uri":"swr_faq_0006.html",
+ "node_id":"swr_faq_0006.xml",
"product_code":"swr",
- "code":"29",
+ "code":"36",
"des":"Problem: When you push an image to SWR through your container engine client, the operation fails with the following information returned.denied: you do not have the permi",
"doc_type":"usermanual",
- "kw":"Why Does an Image Fail to Be Uploaded Through a Container Engine Client?,Troubleshooting,User Guide",
+ "kw":"Why Does an Image Fail to Be Uploaded Through a Container Engine Client?,Troubleshooting,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Why Does an Image Fail to Be Uploaded Through a Container Engine Client?",
"githuburl":""
},
{
"uri":"swr_faq_0033.html",
+ "node_id":"swr_faq_0033.xml",
"product_code":"swr",
- "code":"30",
+ "code":"37",
"des":"Problem: When you run the docker pull command to pull an image from SWR, error message \"x509: certificate signed by unknown certificates\" is displayed.Possible Causes:A c",
"doc_type":"usermanual",
- "kw":"Why Does the docker pull Command Fail to Be Executed?,Troubleshooting,User Guide",
+ "kw":"Why Does the docker pull Command Fail to Be Executed?,Troubleshooting,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Why Does the docker pull Command Fail to Be Executed?",
"githuburl":""
},
+ {
+ "uri":"en-us_topic_0000001488475196.html",
+ "node_id":"en-us_topic_0000001488475196.xml",
+ "product_code":"",
+ "code":"38",
+ "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "doc_type":"",
+ "kw":"Other FAQs",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Other FAQs",
+ "githuburl":""
+ },
+ {
+ "uri":"en-us_topic_0000001539235197.html",
+ "node_id":"en-us_topic_0000001539235197.xml",
+ "product_code":"",
+ "code":"39",
+ "des":"If a CCE workload cannot pull an SWR image and the message indicating \"Not logged in\" is displayed, check whether the YAML file of the workload contains the imagePullSecr",
+ "doc_type":"",
+ "kw":"Why Does a CCE Workload Cannot Pull an Image from SWR and the Message Indicating \"Not Logged In\" Is ",
+ "search_title":"",
+ "metedata":[
+ {
+
+ }
+ ],
+ "title":"Why Does a CCE Workload Cannot Pull an Image from SWR and the Message Indicating \"Not Logged In\" Is Displayed?",
+ "githuburl":""
+ },
{
"uri":"swr_change_index.html",
+ "node_id":"swr_change_index.xml",
"product_code":"swr",
- "code":"31",
+ "code":"40",
"des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
"doc_type":"usermanual",
- "kw":"Change History,User Guide",
+ "kw":"Change History,User Manual",
+ "search_title":"",
+ "metedata":[
+ {
+ "prodname":"swr",
+ "documenttype":"usermanual"
+ }
+ ],
"title":"Change History",
"githuburl":""
}
diff --git a/docs/swr/umn/CLASS.TXT.json b/docs/swr/umn/CLASS.TXT.json
index 3fade1c9..daf40846 100644
--- a/docs/swr/umn/CLASS.TXT.json
+++ b/docs/swr/umn/CLASS.TXT.json
@@ -27,7 +27,7 @@
"code":"3"
},
{
- "desc":"You can use SWR to build, push, pull, synchronize, and delete container images.AdvantagesP2P download acceleration ensures faster image pull for CCE clusters.Up to 99.999",
+ "desc":"You can use SWR to build, push, pull, synchronize, and delete container images.AdvantagesPull acceleration ensures faster image pull for CCE clusters.Up to 99.999999999% ",
"product_code":"swr",
"title":"Application Scenarios",
"uri":"swr_03_0004.html",
@@ -53,6 +53,24 @@
"p_code":"1",
"code":"6"
},
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"swr",
+ "title":"Permissions",
+ "uri":"en-us_topic_0000001488156484.html",
+ "doc_type":"usermanual",
+ "p_code":"1",
+ "code":"7"
+ },
+ {
+ "desc":"By default, new IAM users do not have any permissions granted. You need to add them to one or more groups and attach permissions policies or roles to these groups. In thi",
+ "product_code":"swr",
+ "title":"SWR Permissions",
+ "uri":"en-us_topic_0000001488156664.html",
+ "doc_type":"usermanual",
+ "p_code":"7",
+ "code":"8"
+ },
{
"desc":"SWR works with other cloud services and requires permissions to access them. For details, see Figure 1.Cloud Container Engine (CCE)CCE is a high-performance, high-reliabi",
"product_code":"swr",
@@ -60,16 +78,34 @@
"uri":"swr_03_0006.html",
"doc_type":"usermanual",
"p_code":"1",
- "code":"7"
+ "code":"9"
},
{
"desc":"SoftWare Repository for Container (SWR) allows you to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applicatio",
"product_code":"swr",
- "title":"Introduction",
+ "title":"Overview",
"uri":"swr_01_0009.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"8"
+ "code":"10"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"swr",
+ "title":"Permissions Management",
+ "uri":"swr_01_0070.html",
+ "doc_type":"usermanual",
+ "p_code":"",
+ "code":"11"
+ },
+ {
+ "desc":"This section describes how to use IAM for fine-grained permission management on your SWR resources. With IAM, you can:Create IAM users for employees based on your enterpr",
+ "product_code":"swr",
+ "title":"Creating a User and Granting SWR Permissions",
+ "uri":"swr_01_0072.html",
+ "doc_type":"usermanual",
+ "p_code":"11",
+ "code":"12"
},
{
"desc":"The container engine, namely, Docker, is an open-source engine which allows you to create a lightweight, portable, and self-sufficient container for any application. SWR ",
@@ -78,7 +114,7 @@
"uri":"swr_01_0006.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"9"
+ "code":"13"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -87,7 +123,7 @@
"uri":"swr_01_0028.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"10"
+ "code":"14"
},
{
"desc":"This section walks you through the steps of uploading an image to SWR through the client by taking the nginx:v1 image built in Basics of the Container Engine as an exampl",
@@ -95,8 +131,8 @@
"title":"Uploading an Image Through the Client",
"uri":"swr_01_0011.html",
"doc_type":"usermanual",
- "p_code":"10",
- "code":"11"
+ "p_code":"14",
+ "code":"15"
},
{
"desc":"This section describes how to obtain a login command that is valid for a year.For security purposes, it is advised to obtain the login command in the development environm",
@@ -104,8 +140,8 @@
"title":"Obtaining a Long-Term Valid Login Command",
"uri":"swr_01_1000.html",
"doc_type":"usermanual",
- "p_code":"10",
- "code":"12"
+ "p_code":"14",
+ "code":"16"
},
{
"desc":"You can run the docker pull command to pull images from SWR.Run the docker images command to check whether the images are successfully pulled.docker save [Image name:tag ",
@@ -113,8 +149,8 @@
"title":"Pulling an Image",
"uri":"swr_01_0017.html",
"doc_type":"usermanual",
- "p_code":"10",
- "code":"13"
+ "p_code":"14",
+ "code":"17"
},
{
"desc":"After uploading an image, you can set image attributes, including its type (private by default), category and description.Public images can be pulled by all users; wherea",
@@ -122,8 +158,8 @@
"title":"Setting Image Attributes",
"uri":"swr_01_0016.html",
"doc_type":"usermanual",
- "p_code":"10",
- "code":"14"
+ "p_code":"14",
+ "code":"18"
},
{
"desc":"You can share your private images with other users and grant the users access permissions.The user with whom you shared the image can then log in to SWR console to view t",
@@ -131,8 +167,8 @@
"title":"Sharing Private Images",
"uri":"swr_01_0026.html",
"doc_type":"usermanual",
- "p_code":"10",
- "code":"15"
+ "p_code":"14",
+ "code":"19"
},
{
"desc":"Organizations enable efficient management of images. Organizations are used to isolate image repositories. With each organization being limited to one company or departme",
@@ -141,16 +177,16 @@
"uri":"swr_01_0014.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"16"
+ "code":"20"
},
{
- "desc":"To manage SWR permissions, you can use Identity and Access Management (IAM). If you have the SWR Admin or Tenant Administrator permission, you become an admin user of SWR",
+ "desc":"To manage SWR permissions, you can use Identity and Access Management (IAM). If you have the SWR Administrator or Tenant Administrator permission, you become an admin use",
"product_code":"swr",
"title":"User Permissions",
"uri":"swr_01_0015.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"17"
+ "code":"21"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -159,7 +195,7 @@
"uri":"swr_faq_index.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"18"
+ "code":"22"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -167,17 +203,26 @@
"title":"General FAQs",
"uri":"swr_faq_1001.html",
"doc_type":"usermanual",
- "p_code":"18",
- "code":"19"
+ "p_code":"22",
+ "code":"23"
},
{
- "desc":"SWR has no limit on the number of images. You can upload any number of images.SWR has no restriction on the kernel architecture of images. There is no difference between ",
+ "desc":"SoftWare Repository for Container (SWR) allows users to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applicat",
"product_code":"swr",
- "title":"SWR Overview",
+ "title":"What Is SWR?",
+ "uri":"swr_faq_1011.html",
+ "doc_type":"usermanual",
+ "p_code":"23",
+ "code":"24"
+ },
+ {
+ "desc":"SWR has no limit on the number of images. You can upload any number of images.The bandwidth of SWR dynamically changes based on actual usage.The billing items of SWR incl",
+ "product_code":"swr",
+ "title":"About SWR",
"uri":"swr_faq_0013.html",
"doc_type":"usermanual",
- "p_code":"19",
- "code":"20"
+ "p_code":"23",
+ "code":"25"
},
{
"desc":"The following two approaches are for you to consider. Approach 1 is for images that will only be updated occasionally whereas approach 2 is for images that will be freque",
@@ -185,8 +230,8 @@
"title":"How Do I Create a Container Image?",
"uri":"swr_faq_0012.html",
"doc_type":"usermanual",
- "p_code":"19",
- "code":"21"
+ "p_code":"23",
+ "code":"26"
},
{
"desc":"Run the docker save command to compress the container image into a .tar or .tar.gz package. The command format is as follows:docker save [OPTIONS] IMAGE [IMAGE...][OPTION",
@@ -194,8 +239,26 @@
"title":"How Do I Create an Image Package?",
"uri":"swr_faq_0004.html",
"doc_type":"usermanual",
- "p_code":"19",
- "code":"22"
+ "p_code":"23",
+ "code":"27"
+ },
+ {
+ "desc":"No quotas are imposed on SWR images. You can push as many images as you need.Quotas are imposed on the number of organizations a user can create, as shown in Table 1.",
+ "product_code":"swr",
+ "title":"Are There Quotas for SWR Resources?",
+ "uri":"en-us_topic_0000001539549873.html",
+ "doc_type":"usermanual",
+ "p_code":"23",
+ "code":"28"
+ },
+ {
+ "desc":"Symptom: The creation of an organization fails, and a message is displayed indicating that the organization already exists. However, the organization is not found on the ",
+ "product_code":"swr",
+ "title":"Why Does Organization Creation Fail?",
+ "uri":"en-us_topic_0000001488470084.html",
+ "doc_type":"usermanual",
+ "p_code":"23",
+ "code":"29"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -203,8 +266,26 @@
"title":"Image Management FAQs",
"uri":"swr_faq_1002.html",
"doc_type":"usermanual",
- "p_code":"18",
- "code":"23"
+ "p_code":"22",
+ "code":"30"
+ },
+ {
+ "desc":"Currently, SWR does not provide APIs for image push. You can push images using the docker push command on a client or using the SWR console.Currently, SWR does not provid",
+ "product_code":"swr",
+ "title":"Image Push and Pull",
+ "uri":"swr_faq_1012.html",
+ "doc_type":"usermanual",
+ "p_code":"30",
+ "code":"31"
+ },
+ {
+ "desc":"500",
+ "product_code":"swr",
+ "title":"How Many Tenants Can I Share an SWR Private Image with?",
+ "uri":"swr_faq_1013.html",
+ "doc_type":"usermanual",
+ "p_code":"30",
+ "code":"32"
},
{
"desc":"Temporary login commands will expire after 24 hours.Long-term valid login commands are valid for a year.After you obtain a long-term valid login command, your temporary l",
@@ -212,26 +293,8 @@
"title":"What Are the Differences Between Long-Term Valid Login Commands and Temporary Login Commands?",
"uri":"swr_faq_0015.html",
"doc_type":"usermanual",
- "p_code":"23",
- "code":"24"
- },
- {
- "desc":"Assume that a nginx image of v2.0.0 is created on the local Docker client. The docker images command is run to query SIZE of the image. The size is 22.8 MB.Run the docker",
- "product_code":"swr",
- "title":"Why Is an Image Uploaded Through the Client to SWR Different in Size From One Uploaded Through the SWR Console?",
- "uri":"swr_faq_0005.html",
- "doc_type":"usermanual",
- "p_code":"23",
- "code":"25"
- },
- {
- "desc":"Container images stored in SWR cannot be directly downloaded through the console. You can perform the following operations to pull the images:Obtain the image pull comman",
- "product_code":"swr",
- "title":"Can I Pull Container Images on the SWR Console to a Local PC?",
- "uri":"swr_faq_0035.html",
- "doc_type":"usermanual",
- "p_code":"23",
- "code":"26"
+ "p_code":"30",
+ "code":"33"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -239,8 +302,8 @@
"title":"Troubleshooting",
"uri":"swr_faq_2000.html",
"doc_type":"usermanual",
- "p_code":"18",
- "code":"27"
+ "p_code":"22",
+ "code":"34"
},
{
"desc":"Possible causes are as follows:The container engine is not properly installed, in which case the following error is reported:docker: command not foundSolution: Reinstall ",
@@ -248,8 +311,8 @@
"title":"Why Does the Login Command Fail to Be Executed?",
"uri":"swr_faq_0016.html",
"doc_type":"usermanual",
- "p_code":"27",
- "code":"28"
+ "p_code":"34",
+ "code":"35"
},
{
"desc":"Problem: When you push an image to SWR through your container engine client, the operation fails with the following information returned.denied: you do not have the permi",
@@ -257,8 +320,8 @@
"title":"Why Does an Image Fail to Be Uploaded Through a Container Engine Client?",
"uri":"swr_faq_0006.html",
"doc_type":"usermanual",
- "p_code":"27",
- "code":"29"
+ "p_code":"34",
+ "code":"36"
},
{
"desc":"Problem: When you run the docker pull command to pull an image from SWR, error message \"x509: certificate signed by unknown certificates\" is displayed.Possible Causes:A c",
@@ -266,8 +329,26 @@
"title":"Why Does the docker pull Command Fail to Be Executed?",
"uri":"swr_faq_0033.html",
"doc_type":"usermanual",
- "p_code":"27",
- "code":"30"
+ "p_code":"34",
+ "code":"37"
+ },
+ {
+ "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
+ "product_code":"swr",
+ "title":"Other FAQs",
+ "uri":"en-us_topic_0000001488475196.html",
+ "doc_type":"usermanual",
+ "p_code":"22",
+ "code":"38"
+ },
+ {
+ "desc":"If a CCE workload cannot pull an SWR image and the message indicating \"Not logged in\" is displayed, check whether the YAML file of the workload contains the imagePullSecr",
+ "product_code":"swr",
+ "title":"Why Does a CCE Workload Cannot Pull an Image from SWR and the Message Indicating \"Not Logged In\" Is Displayed?",
+ "uri":"en-us_topic_0000001539235197.html",
+ "doc_type":"usermanual",
+ "p_code":"38",
+ "code":"39"
},
{
"desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.",
@@ -276,6 +357,6 @@
"uri":"swr_change_index.html",
"doc_type":"usermanual",
"p_code":"",
- "code":"31"
+ "code":"40"
}
]
\ No newline at end of file
diff --git a/docs/swr/umn/en-us_image_0000001127297210.png b/docs/swr/umn/en-us_image_0000001127297210.png
new file mode 100644
index 00000000..9964a693
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001127297210.png differ
diff --git a/docs/swr/umn/en-us_image_0000001137013964.png b/docs/swr/umn/en-us_image_0000001137013964.png
deleted file mode 100644
index 8e7f5948..00000000
Binary files a/docs/swr/umn/en-us_image_0000001137013964.png and /dev/null differ
diff --git a/docs/swr/umn/en-us_image_0000001154534788.png b/docs/swr/umn/en-us_image_0000001154534788.png
deleted file mode 100644
index 8043ab49..00000000
Binary files a/docs/swr/umn/en-us_image_0000001154534788.png and /dev/null differ
diff --git a/docs/swr/umn/en-us_image_0000001200800369.png b/docs/swr/umn/en-us_image_0000001200800369.png
deleted file mode 100644
index c5dc9779..00000000
Binary files a/docs/swr/umn/en-us_image_0000001200800369.png and /dev/null differ
diff --git a/docs/swr/umn/en-us_image_0000001361665969.png b/docs/swr/umn/en-us_image_0000001361665969.png
new file mode 100644
index 00000000..cdea09f3
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001361665969.png differ
diff --git a/docs/swr/umn/en-us_image_0000001507528236.png b/docs/swr/umn/en-us_image_0000001507528236.png
new file mode 100644
index 00000000..8604d145
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001507528236.png differ
diff --git a/docs/swr/umn/en-us_image_0000001507688112.png b/docs/swr/umn/en-us_image_0000001507688112.png
new file mode 100644
index 00000000..070e8b21
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001507688112.png differ
diff --git a/docs/swr/umn/en-us_image_0000001539405909.png b/docs/swr/umn/en-us_image_0000001539405909.png
new file mode 100644
index 00000000..cff55073
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001539405909.png differ
diff --git a/docs/swr/umn/en-us_image_0000001539605245.png b/docs/swr/umn/en-us_image_0000001539605245.png
new file mode 100644
index 00000000..8bbf3ccc
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001539605245.png differ
diff --git a/docs/swr/umn/en-us_image_0000001558527697.png b/docs/swr/umn/en-us_image_0000001558527697.png
new file mode 100644
index 00000000..2bc934f4
Binary files /dev/null and b/docs/swr/umn/en-us_image_0000001558527697.png differ
diff --git a/docs/swr/umn/en-us_topic_0000001488156484.html b/docs/swr/umn/en-us_topic_0000001488156484.html
new file mode 100644
index 00000000..28e7c883
--- /dev/null
+++ b/docs/swr/umn/en-us_topic_0000001488156484.html
@@ -0,0 +1,19 @@
+
+
+Permissions
+If you need to assign different permissions to employees in your enterprise to access your SWR resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, enabling secure access to your cloud resources.
+
With IAM, you can use your account to create IAM users, and assign permissions to the users to control their access to specific cloud resources. For example, some software developers in your enterprise need to use SWR resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using SWR resources.
+
If your account does not require individual IAM users for permissions management, skip this section.
+
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
+
SWR Permissions
+By default, new IAM users do not have any permissions granted. You need to add them to one or more groups and attach permissions policies or roles to these groups. In this way, the users can inherit permissions from the groups and perform operations on specific cloud resources.
+
SWR is a project-level service deployed and accessed in specific physical regions. To assign AOM permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing SWR, the users need to switch to a Region where they have been authorized to use this service.
+
+
Table 1 SWR permissionsName
+ |
+Description
+ |
+Type
+ |
+
|---|
+
+SWR Administrator
+ |
+SWR administrator permissions, including all SWR permissions.
+ |
+System-defined role
+ |
+
+Tenant Administrator
+ |
+Administrator permissions for all services except IAM, including all SWR permissions.
+ |
+System-defined role
+ |
+
+Tenant Guest
+ |
+Read-only permissions for all services except IAM, including permissions such as image pull.
+ |
+System-defined role
+ |
+
+ServiceStage Developer
+ |
+ServiceStage developer permissions, including permissions such as image pull.
+ |
+System-defined role
+ |
+
+
+
+
+
- Granting user permissions enables you to grant read, write, and management permissions to different users for them to access either a specific image or images of a specific organization.
+
+
Why Does Organization Creation Fail?
+Symptom: The creation of an organization fails, and a message is displayed indicating that the organization already exists. However, the organization is not found on the Organizations page.
+
Solution: Change the organization name to one which is globally unique in the Region.
+
If a message is displayed indicating that the organization already exists, the organization name may have been used by another user. Use another organization name.
+
Other FAQs
+
+
+
diff --git a/docs/swr/umn/en-us_topic_0000001539235197.html b/docs/swr/umn/en-us_topic_0000001539235197.html
new file mode 100644
index 00000000..1ea6ad33
--- /dev/null
+++ b/docs/swr/umn/en-us_topic_0000001539235197.html
@@ -0,0 +1,34 @@
+
+
+Why Does a CCE Workload Cannot Pull an Image from SWR and the Message Indicating "Not Logged In" Is Displayed?
+If a CCE workload cannot pull an SWR image and the message indicating "Not logged in" is displayed, check whether the YAML file of the workload contains the imagePullSecrets field and whether the value of name is fixed to default-secret.
+
Example:
+
apiVersion: extensions/v1beta1
+kind: Deployment
+metadata:
+ name: nginx
+spec:
+ replicas: 1
+ selector:
+ matchLabels:
+ app: nginx
+ strategy:
+ type: RollingUpdate
+ template:
+ metadata:
+ labels:
+ app: nginx
+ spec:
+ containers:
+ - image: nginx
+ imagePullPolicy: Always
+ name: nginx
+ imagePullSecrets:
+ - name: default-secret
+
Are There Quotas for SWR Resources?
+No quotas are imposed on SWR images. You can push as many images as you need.
+
Quotas are imposed on the number of organizations a user can create, as shown in Table 1.
+
+
Table 1 SWR resource quotasResource Type
+ |
+Quota
+ |
+
|---|
+
+Organization
+ |
+5
+ |
+
+
+
+
+
Importing an Image File
This section describes how to import an image package as an image using the docker load command.
+
There are two modes:
+
docker load < Path/File name.tar
+
docker load --input Path/File name.tar or docker load -i Path/File name.tar
+
Sample:
+
$ docker load --input fedora.tar
+
Introduction
+Overview
SoftWare Repository for Container (SWR) allows you to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applications.
SWR provides private image repositories and fine-grained permission management, allowing you to grant different access permissions, namely, read, write, and edit, to different users.
-
Figure 1 How SWR works
+
Figure 1 How SWR works
Uploading an Image Through the Client
Scenario
This section walks you through the steps of uploading an image to SWR through the client by taking the nginx:v1 image built in Basics of the Container Engine as an example. Uploading an image through the client is to run Docker commands on the client where Docker is installed to push the image to an image repository of SWR.
-
Each image layer uploaded through the client cannot exceed 10 GB.
-
Notes and Constraints
- Each image layer uploaded through the client cannot exceed 10 GB.
- The Docker client version must be 1.11.2 or later.
@@ -12,8 +10,8 @@
"{
Intranet address}"
]
}
-
To obtain the value of {Intranet address}, log in to the SWR console. On the Dashboard page, click Generate Login Command and obtain the private network address (IP:20202) in the private network command.
-
Figure 1 Obtaining the private network address
+
To obtain the value of {Intranet address}, log in to the SWR console. On the Dashboard page, click Generate Login Command and obtain the private network address in the private network command.
+
Figure 1 Obtaining the private network address
If insecure-registry has been configured in the DOCKER_OPTS configuration item in the /etc/default/docker file, you do not need to modify the /etc/docker/daemon.json file.
Run the following command to add the private network IP address to the end of the DOCKER_OPTS configuration item:
vi /etc/default/docker
@@ -25,7 +23,7 @@
-
Procedure
- Access SWR.
- Log in to the SWR console and the VM running the container engine as the root user.
- In the navigation pane on the left, choose My Images and then click Upload Through Client. On the page displayed, click Generate a temporary docker login command and click
to copy the command.Figure 2 Obtaining a docker login command
+Procedure
- Access SWR.
- Log in to the SWR console and the VM running the container engine as the root user.
- In the navigation pane on the left, choose My Images and then click Upload Through Client. On the page displayed, click Generate a temporary docker login command and click to copy the command.
Figure 2 Obtaining a docker login command
- A temporary login command is valid for 24 hours. For details about how to obtain a login command that will remain valid for a long term, see Obtaining a Long-Term Valid Login Command. After you obtain a long-term valid login command, your temporary login commands will still be valid as long as they are in their validity periods.
- The domain name at the end of the login command is the image repository address. Record the address for later use.
- Run the docker login command on your Docker client (a device that has Docker installed).
The message "Login Succeeded" will be displayed upon a successful login.
@@ -46,6 +44,8 @@ v1: digest: sha256:eb7e3bbd8e3040efa71d9c2cacfa12a8e39c6b2ccd15eac12bdc49e0b66ce
To view the pushed image, refresh the My Images page.
diff --git a/docs/swr/umn/swr_01_0014.html b/docs/swr/umn/swr_01_0014.html
index 07c5951c..a0602a35 100644
--- a/docs/swr/umn/swr_01_0014.html
+++ b/docs/swr/umn/swr_01_0014.html
@@ -3,20 +3,21 @@
Organization Management
Scenario
Organizations enable efficient management of images. Organizations are used to isolate image repositories. With each organization being limited to one company or department, images can be managed in a centralized and efficient manner. An image name needs to be unique within an organization. The same user can access different organizations as long as the user has sufficient permissions, as shown in Figure 1.
You can grant different permissions, namely, read, write, and manage, to users created by the same account. For details, see User Permissions.
-
Figure 1 Organization
+
Figure 1 Organization
Creating an Organization
You can create organizations based on the organizational structure of your enterprise to facilitate image resource management. Create an organization before you push an image.
-
- Log in to the SWR console.
- In the navigation pane on the left, choose Organization Management and click Create Organization. On the page displayed, specify Organization Name and click OK.
Figure 2 Creating an Organization
+- Log in to the SWR console.
- In the navigation pane on the left, choose Organization Management and click Create Organization. On the page displayed, specify Organization Name and click OK.
Figure 2 Creating an organization
- The organization name must be globally unique. If a message is displayed indicating that the organization already exists, the organization name may have been used by another user. Use another organization name.
- After a tenant is deleted, residual organization resources may exist. In this case, the message indicating that the organization already exists could also be displayed when you create an organization. Use another organization name.
Viewing the Images of an Organization
After you create an organization and push images to it, you can view the image list of the organization.
-
- Log in to the SWR console.
- In the navigation pane, choose Organization Management. On the page displayed, click the desired organization name in the list.
- To view the images of this organization, click the Image tab.
Figure 3 Viewing the Images of an Organization
+- Log in to the SWR console.
- In the navigation pane, choose Organization Management. On the page displayed, click the desired organization name in the list.
- To view the images of this organization, click the Images tab.
Figure 3 Viewing the images of an organization
+
Deleting an Organization
Before deleting an organization, delete all the images in the organization.
-
- Log in to the SWR console.
- In the navigation pane, choose Organization Management. On the page displayed, click the desired organization name in the list.
- Click Delete in the upper right corner. In the displayed dialog box, enter DELETE as prompted and click Yes.
+
- Log in to the SWR console.
- In the navigation pane, choose Organization Management. On the page displayed, click the desired organization name in the list.
- Click Delete in the upper right corner. In the displayed dialog box, enter DELETE as prompted and click Yes.
Before you delete a tenant, delete its organizations first; otherwise, residual organization resources may exist. When you create an organization that has the same name with the residual organization, a message is displayed indicating that the organization already exists.
diff --git a/docs/swr/umn/swr_01_0015.html b/docs/swr/umn/swr_01_0015.html
index a549c4db..463f20ba 100644
--- a/docs/swr/umn/swr_01_0015.html
+++ b/docs/swr/umn/swr_01_0015.html
@@ -1,27 +1,27 @@
User Permissions
-
Scenarios
To manage SWR permissions, you can use Identity and Access Management (IAM). If you have the SWR Admin or Tenant Administrator permission, you become an admin user of SWR. You can grant permissions to other IAM users in SWR.
-
If you are not an SWR admin user, you can request an SWR admin user to grant you permissions to read, write, or manage a specific image or images in a specific organization.
-
- An admin user is granted image management permission of all organizations by default, even if the user is not in the authorized user list of the organizations.
- SWR is deployed and accessed in specific physical regions. To assign permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect.
+
Scenario
To manage SWR permissions, you can use Identity and Access Management (IAM). If you have the SWR Administrator or Tenant Administrator permission, you become an admin user of SWR accounts. You can grant permissions to other IAM users in SWR.
+
If you are not an SWR account admin user, you can request an SWR account admin user to grant you permissions to read, write, or manage a specific image or images in a specific organization.
+
- An SWR account admin user is granted image management permission of all organizations by default, even if the user is not in the authorized user list of the organizations.
- SWR is deployed and accessed in specific physical regions. To assign permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect.
Authorization Method
You can grant permissions to users in SWR by using either of the following methods:
-
Granting Permissions for a Specific Image
To allow users to read, write, and manage a specific image, grant corresponding permissions to them on the details page of this image.
-
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the desired image.
- On the image details page, click the Permissions tab.
- Click Add Permission. On the page displayed, click Read, Write, or Manage in the row of the desired username. Click OK to confirm.
Figure 2 Granting Permissions for a Specific Image
+- Log in to the SWR console.
- In the navigation pane, choose My Images and click the desired image.
- On the image details page, click the Permissions tab.
- Click Add Permission. On the page displayed, click Read, Write, or Manage in the row of the desired username. Click OK to confirm.
Figure 2 Granting permissions for a specific image
Modifying or Deleting Permissions for a Specific Image
You can also modify or delete user permissions on the image details page.
-
- To modify permissions, click Modify in the row of the desired username on the Permissions tab page. Select a permission in the Permission drop-down list, and click Save in the Operation column.
- To delete permissions, click Delete in the row of the desired username on the Permissions tab page. In the dialog box displayed, enter DELETE and click Yes.
+
- To modify permissions, click Modify in the row of the desired username on the Permissions tab page. Select a permission in the Permission drop-down list, and click Save in the Operation column.
- To delete permissions, click Delete in the row of the desired username on the Permissions tab page, enter DELETE in the dialog box displayed, and then click Yes.
Granting Permissions for an Organization
To allow users to read, write, and manage all the images in an organization, grant corresponding permissions to them on the details page of this organization.
Only users with the Manage permission can grant permissions for other users.
-
- Log in to the SWR console.
- In the navigation pane, choose Organization Management. Then click Details in the row of the desired organization.
- On the Users tab page, click Add Permission. In the dialog box displayed, select permissions for users and click OK.
+
- Log in to the SWR console.
- In the navigation pane, choose Organization Management. Then click Details in the row of the desired organization.
- On the Users tab page, click Add Permission. In the dialog box displayed, select permissions for users and click OK.
Modifying or Deleting Permissions for an Organization
You can also modify and delete user permissions of an organization.
- To modify permissions, click Modify in the row of the desired username on the Users tab page. Select a permission in the Permission drop-down list, and click Save in the Operation column.
- To delete permissions, click Delete in the row of the desired username on the Users tab page. In the dialog box displayed, enter DELETE and click Yes.
diff --git a/docs/swr/umn/swr_01_0016.html b/docs/swr/umn/swr_01_0016.html
index c9bd0a73..d69e5bb1 100644
--- a/docs/swr/umn/swr_01_0016.html
+++ b/docs/swr/umn/swr_01_0016.html
@@ -4,7 +4,7 @@
Scenario
After uploading an image, you can set image attributes, including its type (private by default), category and description.
Public images can be pulled by all users; whereas the access to private images requires corresponding permissions. You can add permissions, namely, read, write, and manage, to allow users to access your private images. For details, see Granting Permissions for a Specific Image.
-
Procedure
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the desired image.
- On the details page, click Edit in the upper right corner. On the page displayed, set Sharing Type (Public or Private), Category, and Description, and click OK.
Figure 1 Setting Image Attributes
+Procedure
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the desired image.
- On the details page, click Edit in the upper right corner. On the page displayed, set Sharing Type (Public or Private), Category, and Description, and click OK.
Figure 1 Setting Image Attributes
Table 1 Editing an imageParameter
|
diff --git a/docs/swr/umn/swr_01_0017.html b/docs/swr/umn/swr_01_0017.html
index c6d43e7b..6ff40af1 100644
--- a/docs/swr/umn/swr_01_0017.html
+++ b/docs/swr/umn/swr_01_0017.html
@@ -3,8 +3,9 @@
Pulling an Image
Scenario
You can run the docker pull command to pull images from SWR.
-
Procedure
- Log in to the VM running the container engine as the root user.
- Obtain a login command by referring to Step 1 and access SWR.
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the target image.
- On the Image Tags tab page, in the same row as the target image tag, click
in the Image Pull Command column to copy the command.Figure 1 Obtaining the image pull command
- - Run the image pull command obtained in Step 5 on the VM.
Run the docker images command to check whether the images are successfully pulled.
+
+Procedure
- Log in to the VM running the container engine as the root user.
- Obtain a login command by referring to 1 and access SWR.
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the target image.
- On the Image Tags tab page, in the same row as the target image tag, click in the Image Pull Command column to copy the command.
Figure 1 Obtaining the image pull command
+ - Run the image pull command obtained in 5 on the VM.
Run the docker images command to check whether the images are successfully pulled.
# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
xxx/group/nginx v2.0.0 22f2bf2e2b4f 5 hours ago 22.8MB
diff --git a/docs/swr/umn/swr_01_0026.html b/docs/swr/umn/swr_01_0026.html
index 395c4c00..c33c13cc 100644
--- a/docs/swr/umn/swr_01_0026.html
+++ b/docs/swr/umn/swr_01_0026.html
@@ -6,7 +6,7 @@
Notes and Constraints
- Only private images can be shared. Public images cannot be shared.
- Only users authorized to manage the private images can share images. The users with whom you share your images only have the read-only permission, which only allows them to pull the images.
- You can share images only with accounts in the same region. Cross-region image sharing is not supported.
Procedure
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the target image.
- On the details page, click the Sharing tab.
- Click Share Image. Set parameters based on Table 1, and click OK.
Figure 1 Sharing an image
+Procedure
- Log in to the SWR console.
- In the navigation pane, choose My Images and click the target image.
- On the details page, click the Sharing tab.
- Click Share Image. Set parameters based on Table 1, and click OK.
Figure 1 Sharing an image
Table 1 Sharing an imageParameter
|
diff --git a/docs/swr/umn/swr_01_0070.html b/docs/swr/umn/swr_01_0070.html
new file mode 100644
index 00000000..5a4990e2
--- /dev/null
+++ b/docs/swr/umn/swr_01_0070.html
@@ -0,0 +1,11 @@
+
+
+Permissions Management
+
+
+
diff --git a/docs/swr/umn/swr_01_0072.html b/docs/swr/umn/swr_01_0072.html
new file mode 100644
index 00000000..99aa24b1
--- /dev/null
+++ b/docs/swr/umn/swr_01_0072.html
@@ -0,0 +1,21 @@
+
+
+Creating a User and Granting SWR Permissions
+This section describes how to use IAM for fine-grained permission management on your SWR resources. With IAM, you can:
+
- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing SWR resources.
- Grant only the permissions required for users to perform a specific task.
- Entrust a cloud account or cloud service to perform efficient O&M on your SWR resources.
+
If your account does not need individual IAM users, you may skip over this chapter.
+
This section describes the procedure for granting permissions (see Figure 1).
+
Prerequisite
Learn about the permissions supported by SWR and choose policies or roles according to your requirements.
+
+
Process Flow
Figure 1 Process for granting SWR permissions
+
+
- Create a user group and assign permissions.
Create a user group on the IAM console, and assign the SWR Administrator policy to the group.
+ - Create an IAM user and add the user to a user group.
Create a user on the IAM console and add the user to the group created in 1.
+ - Log in as the IAM user and verify permissions.
+
For security purposes, it is advised to obtain the login command in the development environment.
-Procedure
- Obtain the region project name and image repository address.
- Log in to the management console, click your username in the upper right corner, and click My Credentials.
- On the Project List tab page, search for the project corresponding to the current region.
- Obtain the image repository address by referring to 1.b. The domain name at the end of the login command is the image repository address.
+Process
You can obtain a long-term valid login command as the following process:
+
Figure 1 Process
+
Procedure
- Obtain the programmatic access permission. (If the current user has the permission, skip this step.)
- Log in to the management console as an administrator.
- Click
in the upper left corner and select a region and a project. - Click
in the navigation pane on the left and choose Management & Governance > Identity and Access Management. - Enter the name of the user to whom you want to grant the programmatic access permission in the search box on the Users page.
- Click the user to go to its details page.
- Click
next to Access Type. - Select Programmatic access. (You can select only programmatic access or both access types.)
+ - Obtain the region, project name, and image repository address.
- Log in to the management console, click your username in the upper right corner, and click My Credentials.
- On the Projects tab page, search for the project corresponding to the current region.
- Obtain the image repository address by referring to 1.b. The domain name at the end of the login command is the image repository address.
- Obtain an AK/SK.
The access key ID (AK) and secret access key (SK) are a pair of access keys used together to authenticate users who wish to make API requests. The AK/AS pair provides functions similar to a password. If you already have an AK/SK, skip this step.
- Log in to the management console, click your username in the upper right corner, and click My Credentials.
- On the Access Keys tab page, click Add Access Key.
- Enter the login password and verification code sent to your mailbox or mobile phone.
- Download the access key, which includes the AK and SK.
Keep the access key secure and do not disclose it to any unauthorized personnel.
- Log in to a Linux PC and run the following command to obtain the login key:
printf "$AK" | openssl dgst -binary -sha256 -hmac "$SK" | od -An -vtx1 | sed 's/[ \n]//g' | sed 'N;s/\n//'
-In the command, $AK and $SK indicate the AK and SK obtained in Step 2 respectively.
-Figure 1 Sample command output
+In the command, $AK and $SK indicate the AK and SK obtained in 3 respectively.
+Figure 2 Sample command output
- Put the information you obtained in the following format to generate a long-term valid login command:
docker login -u [Regional project name]@[AK] -p [Login key] [Image repository address]
-In the command, the regional project name and image repository address are obtained in Step 1, the AK in Step 2, and the login key in Step 3.
-Figure 2 Long-term login command
+In the command, the regional project name and image repository address are obtained in 2, the AK in 3, and the login key in 4.
The login key is encrypted and cannot be decrypted. Therefore, other users cannot obtain the SK from -p.
The login command can be used on other devices.
diff --git a/docs/swr/umn/swr_03_0001.html b/docs/swr/umn/swr_03_0001.html
index acdd3516..c9eacac6 100644
--- a/docs/swr/umn/swr_03_0001.html
+++ b/docs/swr/umn/swr_03_0001.html
@@ -3,10 +3,10 @@
Introduction
SoftWare Repository for Container (SWR) allows you to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applications.
SWR can either work with CCE or be used as an independent container image repository.
-
Figure 1 How SWR works
+
Figure 1 How SWR works
Features
- Full lifecycle management of images
SWR manages the whole lifecycle of your container images, including push, pull, and deletion.
- Private image repository and access control
Private image repository and fine-grained permission management allow you to grant different access permissions, namely, read, write, and edit, to different users.
- - P2P acceleration of large scale image distribution
SWR uses the image download acceleration technology to ensure faster image pull for CCE clusters in high concurrency scenarios.
+ - Large scale image distribution acceleration
SWR uses the image pull acceleration technology to ensure faster image pull for CCE clusters in high concurrency scenarios.
Accessing SWR
The cloud platform provides a web-based management console and HTTPS-based APIs through which you can access the SWR service.
diff --git a/docs/swr/umn/swr_03_0002.html b/docs/swr/umn/swr_03_0002.html
index fcedb963..3f37da17 100644
--- a/docs/swr/umn/swr_03_0002.html
+++ b/docs/swr/umn/swr_03_0002.html
@@ -5,7 +5,7 @@
Security and Reliability
- SWR supports HTTPS to ensure secure image transmission, and provides multiple security isolation mechanisms between and inside accounts.
- Based on professional storage services, SWR provides highly reliable storage service for your container images.
-
Image Acceleration
- SWR uses the P2P image download acceleration technology to ensure faster image pull for CCE clusters in high concurrency scenarios.
- Intelligent node scheduling around the globe ensures that your image build tasks can be automatically assigned to the idle nodes nearest to the image repository.
+
Image Acceleration
SWR uses the image pull acceleration technology to ensure faster image pull for CCE clusters in high concurrency scenarios.
diff --git a/docs/swr/umn/swr_03_0003.html b/docs/swr/umn/swr_03_0003.html
index 96f78bfe..55844763 100644
--- a/docs/swr/umn/swr_03_0003.html
+++ b/docs/swr/umn/swr_03_0003.html
@@ -9,7 +9,7 @@
Repository
Image repositories are used for storing Docker images. An image repository hosts different versions of a specific containerized application.
Organization
Organizations are used to isolate image repositories. With each organization being limited to one company or department, images can be managed in a centralized and efficient manner. A user can access different organizations as long as the user has corresponding permissions. Different permissions, namely read, write, and manage, can be assigned to different users in the same account.
-
Figure 1 Organization
+
Figure 1 Organization
diff --git a/docs/swr/umn/swr_03_0004.html b/docs/swr/umn/swr_03_0004.html
index ba814c71..82634273 100644
--- a/docs/swr/umn/swr_03_0004.html
+++ b/docs/swr/umn/swr_03_0004.html
@@ -3,10 +3,9 @@
Application Scenarios
Image Lifecycle Management
You can use SWR to build, push, pull, synchronize, and delete container images.
Advantages
-
- P2P download acceleration ensures faster image pull for CCE clusters.
- Up to 99.999999999% image storage reliability is achieved by working with Object Storage Service (OBS).
- Fine-grained authorization allows you to control access to specific images and images in specific organizations.
-
Related Services
-
You can use SWR together with CCE in this scenario.
-
+
- Pull acceleration ensures faster image pull for CCE clusters.
- Up to 99.999999999% image storage reliability is achieved by working with Object Storage Service (OBS).
- Fine-grained authorization allows you to control access to specific images and images in specific organizations.
+
Related service: Cloud Container Engine (CCE)
+
Figure 1 SWR working with CCE
diff --git a/docs/swr/umn/swr_03_0006.html b/docs/swr/umn/swr_03_0006.html
index 56bdc33f..a4b54c17 100644
--- a/docs/swr/umn/swr_03_0006.html
+++ b/docs/swr/umn/swr_03_0006.html
@@ -2,7 +2,7 @@
Related Services
SWR works with other cloud services and requires permissions to access them. For details, see Figure 1.
-
Figure 1 Relationship between SWR and other services
+
Figure 1 Relationship between SWR and other services
- Cloud Container Engine (CCE)
CCE is a high-performance, high-reliability service through which enterprises can manage containerized applications. CCE supports native Kubernetes applications and tools, allowing you to easily set up a container runtime environment on the cloud.
SWR works seamlessly with CCE to allow you to deploy your images held by SWR on CCE clusters.
- Cloud Trace Service (CTS)
CTS generates traces to enable you to get a history of operations performed on cloud service resources. The content of a trace includes operation requests sent using the management console or open APIs as well as the operation results. You can view all generated traces to query, audit, and backtrack performed operations.
diff --git a/docs/swr/umn/swr_faq_0005.html b/docs/swr/umn/swr_faq_0005.html
deleted file mode 100644
index a1e87f10..00000000
--- a/docs/swr/umn/swr_faq_0005.html
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-Why Is an Image Uploaded Through the Client to SWR Different in Size From One Uploaded Through the SWR Console?
-Symptom
Assume that a nginx image of v2.0.0 is created on the local Docker client. The docker images command is run to query SIZE of the image. The size is 22.8 MB.
-
$ docker images
-REPOSITORY TAG IMAGE ID CREATED SIZE
-nginx v2.0.0 22f2bf2e2b4f 9 days ago 22.8MB
-
- Run the docker push command to upload the image to SWR. The size of the image is 9.5 MB.
-
- On the local Docker client, pack the image into a .tar package. Download the nginx.tar package to the local host, and upload the package to SWR. The size of the package is 23.2 MB.
-
-
The size of the image uploaded through the client is different from that of the image uploaded through the SWR console.
-
-
Cause Analysis
Image layers are compressed into .tgz packages when images are uploaded to SWR through the client, whereas when they are uploaded through the SWR console, they are only packed without being compressed. Therefore, the same image will be of different sizes when it is uploaded in these two different ways.
-
-
name invalid: 'repository' is invalid
Possible cause: The organization name or image name does not comply with the naming rules.
Solution: The regular expressions of the organization (namespace) name and image (repository) name are as follows:
-Organization name: The value contains a maximum of 64 characters and must meet regular expression ^([a-z]+(?:(?:(?:_|__|[-]*)[a-z0-9]+)+)?)$.
-Image name: The value contains a maximum of 128 characters and must meet regular expression ^([a-z0-9]+(?:(?:(?:_|__|[-]*)[a-z0-9]+)+)?)$.
+namespace: The value contains a maximum of 64 characters and must meet regular expression ^([a-z]+(?:(?:(?:_|__|[-]*)[a-z0-9]+)+)?)$.
+repository: The value contains a maximum of 128 characters and must meet regular expression ^([a-z0-9]+(?:(?:(?:_|__|[-]*)[a-z0-9]+)+)?)$.
Specify a valid organization name or image name, and push the image again.
-
Image Push Occasionally Times Out
Problem: Image push occasionally times out.
-
Solution: When you push an image from a server in Chinese mainland to a server outside Chinese mainland, the network may be unstable.
-
diff --git a/docs/swr/umn/swr_faq_0012.html b/docs/swr/umn/swr_faq_0012.html
index afdf1d30..aeeb0a9a 100644
--- a/docs/swr/umn/swr_faq_0012.html
+++ b/docs/swr/umn/swr_faq_0012.html
@@ -4,7 +4,7 @@
The following two approaches are for you to consider. Approach 1 is for images that will only be updated occasionally whereas approach 2 is for images that will be frequently updated.
- Approach 1: creating a snapshot. This approach involves three key steps: (1) Start a base container by running a base image (for example, Ubuntu image); (2) install the container engine software inside the base container; (3) create a snapshot of the container.
- Approach 2: creating a Dockerfile to build an image. This approach involves two key steps: (1) Write software installation instructions into a Dockerfile; (2) run the docker build command to build an image from the Dockerfile.
Approach 1: Creating a Snapshot
This approach is suitable for images that will only be updated occasionally.
-
+
Figure 1 Creating a snapshot
Procedure:
- Install the container engine software on a host.
- Start an empty base container in the interactive mode.
For example, start a CentOS container in the interactive mode.
docker run -it centos
@@ -13,13 +13,13 @@
cd bwa;make
Install Git in advance and check whether an SSH key is set on the local host.
- - Run the exit command to exit the container.
- Create a snapshot.
docker commit -m "xx" -a "test" container-id test/image:tag- -a: indicates the author of the base image.
- container-id: indicates the ID of the container you have started in step 2. You can run the docker ps -a command to query the container ID.
- -m: indicates the commit message.
- test/image:tag: indicates the repository name/image name:tag name.
+
- Run the exit command to exit the container.
- Create a snapshot.
docker commit -m "xx" -a "test" container-id test/image:tag- -a: indicates the author of the base image.
- container-id: indicates the ID of the container you have started in step 2. You can run the docker ps -a command to query the container ID.
- -m: indicates the commit message.
- test/image:tag: indicates the repository name/image name:tag name.
- Run the docker images command to list the built container image.
Approach 2: Creating a Dockerfile to Build an Image
This approach is suitable for images that will be frequently updated. In Approach 1, you create a snapshot of the whole container. This could be demanding if you need to frequently update your images. In this case, Approach 2 is put forward to automate the image build process.
The idea behind Approach 2 is to write the process of Approach 1 into a Dockerfile and then run the docker build -t test/image:tag. command to automatically build an image from the Dockerfile. In the preceding command, . indicates the path to the Dockerfile.
-
+
Figure 2 Creating a Dockerfile to build an image
Example Dockerfile:
If an external network is required, ensure that network connectivity is available.
diff --git a/docs/swr/umn/swr_faq_0013.html b/docs/swr/umn/swr_faq_0013.html
index 060ddfd4..6e74dee6 100644
--- a/docs/swr/umn/swr_faq_0013.html
+++ b/docs/swr/umn/swr_faq_0013.html
@@ -1,13 +1,16 @@
-
SWR Overview
+
About SWR
How Many Images Can Be Stored in SWR?
SWR has no limit on the number of images. You can upload any number of images.
-
Can I Push Arm-based Container Images to SWR?
SWR has no restriction on the kernel architecture of images. There is no difference between pushing an Arm-based image and an x86-based image to SWR.
+
What Is the Bandwidth of SWR?
The bandwidth of SWR dynamically changes based on actual usage.
-
What Protocol Is Used to Push Images to SWR When I Run the docker push Command?
HTTPS is used.
+
Is SWR Charged?
The billing items of SWR include storage space and traffic. Currently, it is free of charge.
-
Will an Image Be Overwritten If I Push an Image That Have the Same Name and Tag with it?
Yes, the original image will be overwritten.
+
Does SWR Support Querying the CPU Architecture (x86 or Arm) of an Image?
- For a public image, you can log in to the SWR console, go to the image center, search for the target image, and view its details, including the architectures supported by the image.
+
- For a private image, you can Run docker inspect [Image name:Version name] to query the image architecture.
+
Example: docker inspect openjdk:7.
+
Figure 1 Example
@@ -16,3 +19,10 @@
+
+
\ No newline at end of file
diff --git a/docs/swr/umn/swr_faq_0016.html b/docs/swr/umn/swr_faq_0016.html
index e351683a..a8cff298 100644
--- a/docs/swr/umn/swr_faq_0016.html
+++ b/docs/swr/umn/swr_faq_0016.html
@@ -11,11 +11,10 @@
- The image repository address in the login command is incorrect, in which case the following error is reported:
Error llgging in to v2 endpoint, trying next endpoint: Get https://{{endpoint}}/v2/: dial tcp: lookup {{endpoint}} on xxx.xxx.xxx.xxx:53 : no such host
Solutions:
- Change the image repository address in the login command.
- Generate a temporary login command. For detailed instructions, see 2.
- - x509: certficate has expired or is not yet valid
The preceding error is reported when the AK/SK in the login command with long-term validity is deleted. In this case, use a valid AK/SK to generate a login command.
- - x509: certficate signed by unknown authority
Possible Causes:
-The container engine client communicates with SWR through HTTPS. The client verifies the server certificate. If the server certificate is not issued by an authoritative organization, the following error message is displayed: "x509: certficate signed by unknown authority".
-
-Solutions:
+ - x509: certificate has expired or is not yet valid
The preceding error is reported when the AK/SK in the login command with long-term validity is deleted. In this case, use a valid AK/SK to generate a login command.
+ - x509: certificate signed by unknown authority
Possible Causes:
+The container engine client communicates with SWR through HTTPS. The client verifies the server certificate. If the server certificate is not issued by an authoritative organization, the following error message is displayed: "x509: certificate signed by unknown authority"
+Solutions:
If you trust the server and skip certificate authentication, manually configure Docker startup parameters as follows:
-
-
\ No newline at end of file
diff --git a/docs/swr/umn/swr_faq_0033.html b/docs/swr/umn/swr_faq_0033.html
index 0b5b6718..900d641a 100644
--- a/docs/swr/umn/swr_faq_0033.html
+++ b/docs/swr/umn/swr_faq_0033.html
@@ -5,17 +5,17 @@
Possible Causes:
- A container engine client and SWR communicate with each other using HTTPS. When the client verifies the server certificate and finds that the root certificate installed on the client is incomplete, the error message "x509: certificate signed by unknown certificates" is displayed.
- A proxy is configured on the container engine client.
Solution:
-
- If you trust the server, skip certificate authentication. Specifically, manually configure the container engine startup parameters using either of the following two methods. Replace Image repository address with the actual SWR repository address.
- Add the following configuration to the /etc/docker/daemon.json file. If the file does not exist, manually create it. Ensure that two-space indents are used in the configuration.
{
+- If you trust the server and skip certificate authentication, manually configure the startup parameters for the container engine using either of the following methods (use the actual image repository address):
-
After configuration, run the systemctl restart docker or service restart docker command to restart the container engine.
+After configuration, run the systemctl restart docker or service docker start command to restart the container engine.
- Run the docker info command to check whether the proxy is correctly configured. If not, modify the configuration.
Error: remote trust data does not exist
Problem: When you run the docker pull command to pull an image from SWR, message "Error: remote trust data does not exist" is displayed.
Possible cause: The image signature verification is enabled on the client. However, the image to be pulled does not contain a signature layer.
-
Solution: Check whether the environment variable DOCKER_CONTENT_TRUST is set to 1. If yes, delete DOCKER_CONTENT_TRUST=1 from the /etc/profile file and run the source /etc/profile command to make the modification take effect.
+
Solution: Check whether the environment variable DOCKER_CONTENT_TRUST is set to 1. If yes, delete DOCKER_CONTENT_TRUST=1 from the /etc/profile file and run the source /etc/profile command to make the modification take effect.
diff --git a/docs/swr/umn/swr_faq_0035.html b/docs/swr/umn/swr_faq_0035.html
deleted file mode 100644
index 0a0cda2e..00000000
--- a/docs/swr/umn/swr_faq_0035.html
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
Can I Pull Container Images on the SWR Console to a Local PC?
-
Container images stored in SWR cannot be directly downloaded through the console. You can perform the following operations to pull the images:
-
- Obtain the image pull command on the image details page.
- Run the obtained command on the device where the Docker client is installed.
Example:
-docker pull swr.eu-de.otc.t-systems.com/group/nginx:v1
- - Save the image as a TAR or TAR.GZ file.
Example:
-docker save nginx:v1 > nginx.tar
- - Download the file to the local host.
-
-
-
diff --git a/docs/swr/umn/swr_faq_1001.html b/docs/swr/umn/swr_faq_1001.html
index cd5d3ba3..936a03e7 100644
--- a/docs/swr/umn/swr_faq_1001.html
+++ b/docs/swr/umn/swr_faq_1001.html
@@ -4,12 +4,18 @@
diff --git a/docs/swr/umn/swr_faq_1002.html b/docs/swr/umn/swr_faq_1002.html
index 1261418c..cb96f765 100644
--- a/docs/swr/umn/swr_faq_1002.html
+++ b/docs/swr/umn/swr_faq_1002.html
@@ -4,12 +4,12 @@
diff --git a/docs/swr/umn/swr_faq_1011.html b/docs/swr/umn/swr_faq_1011.html
new file mode 100644
index 00000000..82466e78
--- /dev/null
+++ b/docs/swr/umn/swr_faq_1011.html
@@ -0,0 +1,11 @@
+
+
+
What Is SWR?
+
SoftWare Repository for Container (SWR) allows users to easily manage the full lifecycle of container images and facilitates secure deployment of images for your applications.
+
+
+
diff --git a/docs/swr/umn/swr_faq_1012.html b/docs/swr/umn/swr_faq_1012.html
new file mode 100644
index 00000000..6d78f950
--- /dev/null
+++ b/docs/swr/umn/swr_faq_1012.html
@@ -0,0 +1,27 @@
+
+
+
Image Push and Pull
+
How Do I Push an Image to SWR by Calling APIs?
Currently, SWR does not provide APIs for image push. You can push images using the docker push command on a client or using the SWR console.
+
+
How Do I Pull an Image from SWR by Calling APIs?
Currently, SWR does not provide APIs for image pull. You can pull images using the docker pull command on a client.
+
+
Can I Push Arm-based Container Images to SWR?
SWR has no restriction on the kernel architecture of images. There is no difference between pushing an Arm-based image and an x86-based image to SWR.
+
+
What Protocol Is Used to Push Images to SWR When I Run the docker push Command?
HTTPS is used.
+
+
Will an Image Be Overwritten If I Push an Image That Have the Same Name and Tag with it?
Yes, the original image will be overwritten.
+
+
Where Are the Images Pulled by Running the docker pull Command Stored?
Images pulled by running the docker pull command are stored on your local hosts. You can run the docker save command to save images into TAR archive files.
+
+
What Is the Maximum Size of an SWR Layer?
If you use the container engine client to push images to SWR, each image layer cannot exceed 10 GB.
+
+
Can SWR Be Accessed over Private Networks? Will I Be Charged for Pushing and Pulling Images over Private Networks?
If your machine and the image repository are in the same region, you can access the image repository through private networks. No additional fees are charged for private network access because you have paid for your servers and EIPs.
+
If your machine and the image repository are in different regions, the node must have access to public networks to pull images from the image repository.
+
+
+
+
diff --git a/docs/swr/umn/swr_faq_1013.html b/docs/swr/umn/swr_faq_1013.html
new file mode 100644
index 00000000..fffecd58
--- /dev/null
+++ b/docs/swr/umn/swr_faq_1013.html
@@ -0,0 +1,11 @@
+
+
+
How Many Tenants Can I Share an SWR Private Image with?
+
+
+
diff --git a/docs/swr/umn/swr_faq_index.html b/docs/swr/umn/swr_faq_index.html
index 19882c4c..edeb3e87 100644
--- a/docs/swr/umn/swr_faq_index.html
+++ b/docs/swr/umn/swr_faq_index.html
@@ -14,6 +14,8 @@
- Troubleshooting
+
- Other FAQs
+
diff --git a/docs/swr/umn/swr_pd_index.html b/docs/swr/umn/swr_pd_index.html
index 759afa39..2937662d 100644
--- a/docs/swr/umn/swr_pd_index.html
+++ b/docs/swr/umn/swr_pd_index.html
@@ -14,6 +14,8 @@
- Notes and Constraints
+
- Permissions
+
- Related Services
|---|
|---|
