Skip to main content

Compile

The fetch speed is slow when compiling nativesdk-glibc

Resolution: Change the source settings as follows:
  1. Open the recipe file:
  2. Add the following line to the file:
  3. Save the recipe file and exit.
  4. Clean and fetch nativesdk-glibc again:
  5. After the commands finish, rebuild according to the original procedure.

Kas reports remote HEAD refers to nonexistent ref

Phenomenon: When you run a kas shell command, the build fails with the following error even though the layer repository is intact:
Resolution: This error is caused by an outdated version of kas. Check your kas version and confirm that it is 4.8 or later:
If the version is earlier than 4.8, upgrade kas and run the command again.

eSDK build fails after switching MACHINE in the same workspace

Phenomenon: When you build the eSDK with a different MACHINE in a workspace that was previously used for another MACHINE, the build fails with an error similar to the following:
Resolution: Clean the robotics package group sstate cache, then rebuild the eSDK:

Build failed due to network unavailability

Phenomenon: When you build the robotics image, the build fails with an error similar to the following:
Resolution: To resolve the build failure, add the following code to enable network access for the do_configure task in the rosx-introspection_2.3.0-1.bb and foxglove-bridge_3.2.6-1.bb recipes:
rosx-introspection_2.3.0-1.bb | foxglove-bridge_3.2.6-1.bb

Docker

Docker is not installed

Phenomenon: Docker is not installed
Resolution: Install Docker with the following commands:

Current user is not in the Docker group

Phenomenon: The current user doesn’t have permission to access the Docker socket:
Resolution:
  1. Add to the Docker group:
  2. Confirm that you are part of the Docker group:
  3. Sign out and sign in again for the access to take effect:

Docker fails to pull images due to network or proxy issues

Phenomenon: Docker cannot reach the remote registry. This is typically due to network restrictions or a missing proxy/mirror configuration:
Resolution: Configure a Docker registry mirror that is accessible from your network environment. The following json configuration uses an example Qualcomm registry mirror; replace the URL with a mirror that is appropriate for your network.
Warning
  • Don’t include # comments in the JSON configuration file.
  • Using a tab instead of space and other invisible whitespace characters may break the functionality of JSON configuration files and can also lead to docker.service failing to start.
  1. Open or create the Docker daemon configuration file and add a registry-mirrors entry:
    daemon.json
    Following is an example:
    daemon.json example
  2. Restart the Docker service to apply the new settings.
    NoteFor users in China, use an appropriate Docker registry mirror when pulling Docker images.