Compile
The fetch speed is slow when compiling nativesdk-glibc
Resolution
Resolution
Change the source settings as follows:
- Open the recipe file:
- Add the following line to the file:
- Save the recipe file and exit.
- Clean and fetch
nativesdk-glibcagain: - 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
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 installation fails due to missing Perl module dependencies
Phenomenon: When you run the eSDK installer script, the installation fails with the following error:perl-modules package on the host is missing or incomplete. Reinstall the package, then run the installer again:
- Open a new terminal. Don’t source the eSDK environment setup script in this terminal.
- Find the
perl-modulesversion that is available for your host: - Reinstall the package. Replace
<VERSION>with the version returned in the previous step: - Confirm that the
FindBinmodule loads:The command printsFindBin OKwhen the module is available. - Run the eSDK installer again from the directory that contains it:
- Build the robotics image with
devtool:
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
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
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 installedResolution
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
Resolution
- Add to the Docker group:
- Confirm that you are part of the Docker group:
- 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
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.
-
Open or create the Docker daemon configuration file and add a
registry-mirrorsentry:Following is an example:daemon.jsondaemon.json example -
Restart the Docker service to apply the new settings.
NoteFor users in China, use an appropriate Docker registry mirror when pulling Docker images.
Overlay
Overlay repository metadata fails to download with SSL certificate error
Phenomenon: Runingdnf to access the Qualcomm overlay repository, the metadata download fails with an SSL certificate error similar to the following:
Resolution
Resolution
- On the device, check the current system time:
- If the time is incorrect, manually set it to the current time, and then retry the command that failed. Replace the date and time in the following example with the current time:

