# Issue with Including \`mender\` in an Image While Using \`mender-full\`

**URL:** <https://hub.mender.io/t/issue-with-including-mender-in-an-image-while-using-mender-full/8036>\
**Category:** General Discussions\
**Tags:** yocto, mender-client\
**Created:** [October 7, 2025, 4:35pm UTC](https://hub.mender.io/t/issue-with-including-mender-in-an-image-while-using-mender-full/8036 "2025-10-07T16:35:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stan](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/stan/32/2571_2.png) [@Stan](https://hub.mender.io/u/Stan)\
**Post date:** [October 7, 2025, 4:35pm UTC](https://hub.mender.io/t/issue-with-including-mender-in-an-image-while-using-mender-full/8036/1 "2025-10-07T16:35:49Z")

</div>

Hi all,

I’m running into a problem while building a Yocto image with Mender. My goal is to include the `mender-full` integration for automated partition and update handling, **and also have the `mender` CLI available on the device** so I can run commands like `mender --version`.

Here’s the issue:

- When I include the following line in my `local.conf`:

```bitbake
INHERIT += "mender-full"

```

- And try to add `mender` explicitly to my image:

```bitbake
IMAGE_INSTALL:append = " mender"

```

The build fails with the following error:

```auto
ERROR: core-image-minimal-1.0-r0 do_rootfs: Unable to install packages. Command '/workdir/build/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/recipe-sysroot-native/usr/bin/opkg ... install ca-certificates hellocustom helloworld htop mender mender-artifact-info mender-keys packagegroup-core-boot packagegroup-core-ssh-openssh rollback-test run-postinsts vim' returned 255:
 * opkg_solver_install: No candidates to install mender (null)!
 * opkg_finalize_intercepts: Failed to open dir /workdir/build/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/temp/ipktemp//opkg-ClQyck/opkg-intercept-fNgijC: No such file or directory.
 * rm_r: Failed to open dir /workdir/build/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/temp/ipktemp//opkg-ClQyck/opkg-intercept-fNgijC: No such file or directory.

ERROR: Logfile of failure stored in: /workdir/build/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/temp/log.do_rootfs.370110
ERROR: Task (/workdir/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) failed with exit code '1'

```

- If I remove the `INHERIT += "mender-full"` line, the build succeeds and `mender` can be installed. But then I lose the full Mender integration features (`mender-full`) that are required for automated partitioning and update handling.

* * *

On the device, when `mender-full` is included without explicitly adding `mender`, the CLI and service are missing:

```bash
root@qemuarm64:/# which mender
root@qemuarm64:/# mender --version
-sh: mender: not found

root@qemuarm64:/# systemctl status mender
Unit mender.service could not be found.

root@qemuarm64:/# systemctl start mender
Failed to start mender.service: Unit mender.service not found.

root@qemuarm64:/# systemctl enable mender
Failed to enable unit: Unit file mender.service does not exist.

root@qemuarm64:/# journalctl -u mender
-- No entries --

```

* * *

### My Goal

- Keep `mender-full` in the image to enable automated partitioning and rollback features.
- Be able to use `mender` commands on the device (`mender --version`, `mender daemon`, etc.).

* * *

Has anyone encountered this issue or can suggest a proper way to include both `mender-full` **and** the `mender` CLI in a Yocto image without causing the package installation failure?

Thanks in advance for any help!

Stan

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [October 8, 2025, 7:28am UTC](https://hub.mender.io/t/issue-with-including-mender-in-an-image-while-using-mender-full/8036/2 "2025-10-08T07:28:42Z")

</div>

Hi @Stan,

The `mender-full` integration does already install the Mender Client.  
During the version upgrade 3.x → 4.x, the `mender` binary got split into `mender-update` and `mender-auth`. Can you check if those are present?  
Explicitly adding something to `IMAGE_INSTALL` should absolutely not be necessary. You can find more information about the breaking changes at [Upgrading | Mender documentation](https://docs.mender.io/3.7/client-installation/install-with-debian-package/upgrading#upgrade-the-mender-client-3-x-series-to-4-0-0-or-later)

Greetz,  
Josef