在Yocto中添加文件至系统镜像失败问题排查求助

It sounds like you've got a solid starting point with your recipe—no syntax errors is a big win! Let's break down the most likely reasons your files aren't showing up in the final root filesystem, step by step:

1. Verify Your Source Files Are Being Fetched #

First, make sure Yocto is actually pulling your files into the build workspace.

• Run bitbake nested-containers -c fetch -f to force a re-fetch of your sources.
• Navigate to the recipe's working directory (usually at build/tmp/work/<target-arch>/nested-containers/<version>/workdir) and check if rootfs.tar.gz and Dockerfile exist here.
  • If they're missing, double-check that the files are placed in meta-custom/recipes-core/nested-containers/files/ (since your SRC_URI uses file:// which points to the files subdirectory relative to the .bb file).

2. Confirm the do_install Task Is Executing Correctly #

Even if the files are fetched, the install step might not be placing them where expected.

• Re-run the install task with debugging:

  bitbake nested-containers -c install -f
  

• Check the install destination in the staging directory: build/tmp/work/<target-arch>/nested-containers/<version>/image/usr/share/ (since ${datadir} defaults to /usr/share). If your files aren't here, try adding debug echoes to your do_install function:

  do_install () {
      echo "Creating directory: ${D}${datadir}"
      install -d ${D}${datadir}
      echo "Copying rootfs.tar.gz to ${D}${datadir}"
      install -m 755 ${WORKDIR}/rootfs.tar.gz ${D}${datadir}
      echo "Copying Dockerfile to ${D}${datadir}"
      install -m 755 ${WORKDIR}/Dockerfile ${D}${datadir}
  }
  

  Then re-run the install task and check the output for your echo statements to confirm each step runs.

3. Ensure FILES_${PN} Is Including the Files #

Yocto won't package files unless they're explicitly listed in FILES_${PN}.

• Verify the files are included in the package by running:

  oe-pkgdata-util list-files nested-containers
  

  Look for entries like /usr/share/rootfs.tar.gz and /usr/share/Dockerfile.
• If they're missing, try using absolute paths in FILES_${PN} to rule out variable expansion issues:

  FILES_${PN} += " \
      /usr/share/rootfs.tar.gz \
      /usr/share/Dockerfile \
  "
  

4. Check If the Package Is Actually Installed in the Image #

Even if the recipe builds correctly, the package might not be added to your image.

• Confirm nested-containers is in the final IMAGE_INSTALL list:

  bitbake <your-image-name> -e | grep IMAGE_INSTALL
  

  Look for nested-containers in the output. If it's missing, double-check your local.conf entry—IMAGE_INSTALL_append = " nested-containers" needs that leading space to separate it from existing packages.
• You can also re-generate the root filesystem explicitly:

  bitbake <your-image-name> -c rootfs -f
  

  Then check the package list at build/tmp/work/<target-arch>/<your-image>/<version>/rootfs/packaging/package-list for nested-containers.

5. Validate the datadir Variable Expansion #

Occasionally, variable overrides can change the default value of ${datadir}.

• Check what datadir resolves to for your recipe:

  bitbake nested-containers -e | grep datadir
  

  Ensure it matches the path you're using in do_install and FILES_${PN}.

If you work through these steps, you should be able to pinpoint exactly where the process is breaking down. Let me know if any of these checks reveal something unexpected!

内容的提问来源于stack exchange，提问作者fnx_qt