# Rootfs-image: "type" property in type-info empty

**URL:** https://hub.mender.io/t/rootfs-image-type-property-in-type-info-empty/6945
**Category:** General Discussions
**Tags:** mender-artifact
**Created:** [June 12, 2024, 4:21pm UTC](https://hub.mender.io/t/rootfs-image-type-property-in-type-info-empty/6945 "2024-06-12T16:21:22Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![hesmar](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/hesmar/32/1807_2.png) [@hesmar](https://hub.mender.io/u/hesmar)
#### Post date: [June 12, 2024, 4:21pm UTC](https://hub.mender.io/t/rootfs-image-type-property-in-type-info-empty/6945/1 "2024-06-12T16:21:22Z")

</div>

Hi, I use `mender-artifact` in Yocto and notice that the `type` field in `type-info` is empty:

```auto
{
    "type":"",
...
}

```

Shouldn’t that be `rootfs-image`? For other artifacts, e.g. `single-file`, it is correct. If this behavior is intented, is there any other good way to get the artifact type from the header?

---

<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: [June 13, 2024, 10:55am UTC](https://hub.mender.io/t/rootfs-image-type-property-in-type-info-empty/6945/2 "2024-06-13T10:55:25Z")

</div>

Hi @hesmar,

By “in yocto” you mean that you’re using the canonical workflow as provided by `meta-mender`? Or a custom invocation of `mender-artifact`?

Greets,  
Josef

---

<div class="post-metadata">

### Author: ![hesmar](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/hesmar/32/1807_2.png) [@hesmar](https://hub.mender.io/u/hesmar)
#### Post date: [June 13, 2024, 11:53am UTC](https://hub.mender.io/t/rootfs-image-type-property-in-type-info-empty/6945/3 "2024-06-13T11:53:07Z")

</div>

We use `meta-mender` as part of the (modified) [tegra-demo-distro](https://github.com/OE4T/tegra-demo-distro/tree/kirkstone-l4t-r32.7.x) but I could also reproduce the issue by invoking `mender-artifact` manually.
