# InitRamfs x86\_64 producing mender files

**URL:** <https://hub.mender.io/t/initramfs-x86-64-producing-mender-files/270>\
**Category:** General Discussions\
**Tags:** sumo, thud\
**Created:** [March 1, 2019, 10:04pm UTC](https://hub.mender.io/t/initramfs-x86-64-producing-mender-files/270 "2019-03-01T22:04:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [March 1, 2019, 10:04pm UTC](https://hub.mender.io/t/initramfs-x86-64-producing-mender-files/270/1 "2019-03-01T22:04:39Z")

</div>

When creating a yocto x86\_64 image with mender i get duplicate images created in deploy folder prefixed core-image-minimal-initramfs\* as well as the normal images. surely this isnt required as INITRAMFS\_FSTYPES only contains “cpio.gz”.

How can i stop this as its uses twice the storage size.

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [March 2, 2019, 10:10am UTC](https://hub.mender.io/t/initramfs-x86-64-producing-mender-files/270/2 "2019-03-02T10:10:21Z")

</div>

Found the problem, I stupidly has the mender features enable and disable declarations in the machine.conf, when it should be in my image recipe bb file so that they don’t also get applied to core-image-minimal-initramfs IMAGE\_FSTYPES

---

<div class="post-metadata">

**Author:** ![dellgreen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/dellgreen/32/85_2.png) [@dellgreen](https://hub.mender.io/u/dellgreen)\
**Post date:** [March 8, 2019, 3:31pm UTC](https://hub.mender.io/t/initramfs-x86-64-producing-mender-files/270/3 "2019-03-08T15:31:05Z")

</div>

Unfortunately on clean build and retest this creates an image that only boots to grub so it seems like i cannot have the mender enable disable declarations in the image recipe. Hence i’m back to having large mender image file for the core-image-minimal-initramfs and core-image-minimal.  
Is there a specific way that i can stop mender creating its files for the core-image-minimal-initramfs image