Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- What's New
- Function Overview
- Service Overview
-
Getting Started
- Building with Ant and Uploading the Package to a Release Repo (x86, Preset Image, GUI)
- Building with CMake and Uploading the Package to a Release Repo (Arm, Preset Image, GUI)
- Building with Maven, Uploading the Software Package, and Pushing the Image (x86, Preset Image, Code)
- Common Practices for Beginners
-
User Guide
- Working with CodeArts Build
- Enabling CodeArts Build
- Configuring Project-Level Role Permissions
- Creating a Build Task
-
Configuring a Build Task
- Performing Basic Configurations
- Selecting Build Actions
-
Configuring Build Actions
- Building with Maven
- Building with Android
- Building with npm
- Building with Gradle
- Building with Yarn
- Building with Gulp
- Building with Grunt
- Building with Mono
- Building in PHP
- Building with Setuptools
- Building with PyInstaller
- Running Shell Commands
- Building with GNU Arm
- Building with CMake
- Building with Ant
- Building with Kotlin
- Building with Go
- Building Android App with Ionic
- Building an Android Quick App
- Building with sbt
- Building with Grails
- Building with Bazel
- Building with Flutter
- Building with HarmonyOS
- Running Docker Commands to Operate Images
- Generating a Unit Test Report
- Customizing a Build Environment
- Using a Custom Build Environment
- Downloading a Software Package from Release Repos
- Uploading a Software Package to Release Repos
- Uploading Files to OBS
- Configuring Parameters
- Configuring Schedules
- Configuring Roles and Permissions
- Configuring Notifications
- Running a Build Task
- Viewing a Build Task
- Managing Build Tasks
- Querying Audit Logs
- References
- Old User Guide
-
Best Practices
- Creating a Docker Image with a Maven Artifact and Pushing the Image to SWR (Built-in Executors, GUI)
- Building with Maven and Uploading the Software Package to the Self-hosted Repo (Built-in Executors, GUI)
- Building with Maven to Generate a Private Dependency for Another Build (Built-in Executors, GUI)
- Building with npm and Uploading the Software Package to the Release Repo (Built-in Executors, GUI)
- Building with Maven (Custom Executors, GUI)
- Building with Maven, Uploading the Software Package, and Pushing the Image to SWR (Built-in Executors, Code)
- Running a Multi-Task Maven Build Project (Built-in Executors, Code)
- Using the File from the Self-hosted Repo to Build with Maven and Uploading the Resulting Software Package (Built-in Executors, GUI)
- Running a Build Task on a Custom Environment (Built-in Executors, GUI)
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
Task APIs
- Querying Build History in a Specified Period
- Querying Build History
- Downloading the Keystore File
- Viewing Task Status
- Querying Build Tasks in a Project
- Running a Build Task
- Querying the Latest Successful Build with a Specified Code Repository
- Querying Details of a Build Record
- Querying Success Rate of a Build Task in a Specified Period
- Downloading All Build Logs
- Downloading Logs of Build Actions
- Obtaining Information About Build Records
- Obtaining Details About Build Results
- Stopping a Build Task
- Deleting a Build Task
- Disabling a Build Task
- Restoring a Build Task
- Creating a Build Task
- Updating a Build Task
- Querying a Build Template
- Creating a Build Template
- Deleting a Build Template
- Querying Notifications
- Updating Notifications
- Canceling Notifications
- Obtaining Build Task Details
- Downloading Real-time Build Logs
- Obtaining Build Records of a Task
- CodeArts Build (Unavailable Soon)
- Application Examples
- Appendix
- Change History
-
FAQs
-
General
- Can I Run a Build Task with a Specific Server or Server Configuration?
- Why Are the Required Project Files Not Found During Builds?
- Files Not Found During Software Package Upload
- Why Am I Prompted that My Permissions Are Insufficient When Running a Build Task?
- Why Am I Prompted that the Build Task Does Not Exist When Calling It Through a Pipeline?
- Why Is My Task Stopped?
- How Do I Migrate Common Java Projects Created with Eclipse to the Cloud?
- Service Endpoint Did Not Exist
- Incomplete JAR Due to Parallel Build Tasks
- How Do I Resolve the Error Occurred When Pulling the Sub-module During My Build?
- How Do I Fix the Submodules Checkout Error Due to a Failure to Obtain Its Revision?
- Why Are the Submodules Not Being Pulled During My Build?
-
Maven Builds
- What Can I Do If License Check Fails?
- Failed to Upload a Package Using the maven deploy Command
- How Do I Deal With the Missing POM File?
- How Do I Deal With the Missing Package or Symbol?
- Using the exec-maven-plugin Extension for Maven and NPM Hybrid Builds
- How Do I Fix the Errors Related to References Among Multiple Child and Parent Projects?
- How Do I Configure and Clear the Cache for a Maven Build?
- How Do I Find the Correct Build Package Path?
- How Do I Use jib-maven-plugin to Build a Maven Project and Create an Image?
- Why Is the New Package Still Built from the Old Code Even After the Code Has Been Updated?
- Why Is My Download of Maven Components Slow?
-
Android Builds
- How Do I Deal With the Unstable Jcenter () Configured for a Project?
- What Should I Do If an Error Occurs During the Lint Check and the Task Stops?
- What Should I Do When Dependency com.android.tools.build:gradle:3.0.1 Cannot Be Downloaded?
- Why Am I Seeing the Error Message "Javadoc generation failed"?
- Why Am I Seeing the Error Message "Could not find method google()"?
- What Can I Do If the Gradle Version Is Too Early?
- How Do I Fix the Android APK Signing Failure?
- Using Gradle for Build
-
npm Builds
- Why Am I Seeing the Error Message "JavaScript heap out of memory"?
- Why Am I Seeing the Error Message "enoent ENOENT: no such file or directory"?
- Why Am I Seeing the Error Message "Module not found: Error: Can't resolve ..."?
- Why Did My Build Fail Without Displaying Any Errors?
- Why Am I Seeing the Error Message "npm cb() never called"?
- Why Am I Seeing the Error Message "gyp ERR!"? stack Error: EACCES: permission denied
- Why Am I Seeing the Error Message "eslint: error 'CLODOP' is not defined"?
- How Do I Fix the node-sass Download Failure?
- Why Am I Seeing the Error Message "error: Could Not Write Config File"?
- Why Does It Take Long to Install Dependencies and Build?
- What Should I Do When the Dependency Version Cannot Be Found?
-
Images
- Failed to Create an Image Using Dockerfile
- Failed to Push Images to SWR
- How Do I Resolve the Image Pull Failure During a Build Task?
- No Permission to Pull Images When SWR Public Images Are Used
- Failed to Log In to the Image Repository
- How Do I Push an Image to Other Tenants?
- Pulling Docker Hub Images Times Out or Exceeds the Max. Attempts
-
General
- Videos
- General Reference
Copied.
Failed to Push Images to SWR
When you execute the action Build Image and Push to SWR or the action Run Docker Commands, an image may fail to be pushed due to incorrect parameters or environment problems. In this case, rectify the fault by referring to the following solutions provided for different scenarios.
- Insufficient Permissions (denied: you do not have the permission)
- Number of Organizations Reaches the Upper Limit (denied: The number of namespaces exceeds the upper limit)
- You Have Not Logged In (denied: You may not log in yet)
- Authentication Failure (denied: Authenticate Error)
- Invalid Organization Name (invalid reference format)
- The Local Image Does Not Exist (An image does not exist locally with the tag: ***)
- Invalid Abstract (digest invalid: Invalid digest)
Insufficient Permissions
Error Log
When an image is uploaded to SWR, the following error message is displayed:
denied: you do not have the permission [ERROR] : [pluginFrame] step run failed, errorMessage: DEV.CB.0210044, Docker push failed
Analysis and Solution
This error indicates that the current user does not have the permission on the target organization. Check the following possible causes:
- Edit the build task file, click Create Image and Push to SWR, and view the organization name.
- Log in to SWR and check whether the organization exists on the organization management page.
- The organization does not exist. Please create an organization. (The number of organizations cannot exceed the upper limit.)
- If the current user does not have the editing permission for the organization or image that exists in SWR, the preceding error will occur when the image is pushed. The administrator can authorize the current user by referring to User Permissions.
- If the organization exists and the user has the edit permission on the organization, log in to the Identity and Access Management (IAM) console and check whether the user is in a user group with the read-only permission. If yes, remove the user.
Number of Organizations Reaches the Upper Limit
Error Log
denied: The number of namespaces exceeds the upper limit [ERROR] : [pluginFrame] step run failed, errorMessage: DEV.CB.0210044, Docker push failed
Analysis and Solution
By default, if an unused new organization name is specified for pushing an image, SWR automatically creates an organization with the name for the current tenant. SWR limits the number of organizations that can be created by each tenant. If the number of organizations exceeds the limit, the preceding error occurs.
If this error occurs, use the administrator account (or any account with the SWR organization management permissions) to go to the Organization Management page, switch to the corresponding region, view the existing organization list, and select an existing organization or delete unnecessary organizations.
You Have Not Logged In
Error Log
denied: You may not login yet [ERROR] : [pluginFrame] step run failed, errorMessage: fail to execute docker command
Analysis and Solution
The two possible causes are as follows:
- If you have not run the docker login command to log in before pushing an image, add the corresponding login command.
- The login command is executed, but the SWR address in the login command is incorrect. As a result, no error is reported but the login does not take effect. Check whether the login command is correct.
Authentication Failure
Error Log
Error response from daemon: Get https://swr.example.example.com/v2/: denied: Authenticate Error [ERROR] : [pluginFrame] step run failed, errorMessage: fail to execute docker command.
Analysis and Solution
The possible cause is that the account or password in the login command is incorrect or the temporary login information has expired. Obtain a valid login command by referring to Obtaining a Valid Login Command and try again.
Invalid Organization Name
Error Log
invalid reference format [ERROR] : [pluginFrame] step run failed, errorMessage: fail to execute docker command.
Analysis and Solution
The SWR service has requirements on the organization name format. This error occurs when the organization name used to push an image does not meet the format requirements.
If this error occurs, go to the Organization Management page, switch to the corresponding region, and check whether the entered organization name is correct. If yes, manually create an organization with a valid name and try again.
Local Image Does Not Exist
Error Log
[2022-03-05 17:01:05.816] An image does not exist locally with the tag: swr.example.example.com/demo/faqdemo1 [ERROR] : [pluginFrame] step run failed, errorMessage: fail to execute docker command.
Analysis and Solution
The possible cause is that the image fails to be created or the image name and tag in the push command are incorrect. As a result, the expected image in the push command is inconsistent with the image generated from the build or tag command. Check whether the image creation process or push parameters are correct.
In this example, faqdemo1 in the image docker push swr.example.example.com/demo/faqdemo1:v1.1 is incorrect. The image name specified in the build parameter is faqdemo. Modify the push parameter and try again.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot