Comment 12 for bug 1698551

Sorry, but IMHO also #1719102 is something completely different; I'd open a new bug.

In the meantime:

When using fedora 25, it fails in first place with:

2017-11-01 19:04:44.530 | + ostree admin os-init fedora-atomic
2017-11-01 19:04:44.538 | ostree/deploy/fedora-atomic initialized as OSTree root
2017-11-01 19:04:44.539 | + ostree remote add --set=gpg-verify=false fedora-atomic https://kojipkgs.fedoraproject.org/atomic/25/
2017-11-01 19:04:44.548 | + ostree pull fedora-atomic 721fddd24ca1e4cd7b03ca5c7a9382dbb8adfd23eb97cf603d1091c24d1822cb
2017-11-01 19:09:24.669 | error: min-free-space-percent '3%' would be exceeded, 13.7 MB more required

The problem is, that the size computation is IMHO done 'too early' (see https://review.openstack.org/#/c/512085) - and here some disk space is used during the finalize-phase.

As a (temporary) work-around I'd suggest using 'disk-image-create --image-size 5 ...' or similar.

After fixing this, the image creation fails with:

2017-11-01 19:38:08.814 | /tmp/in_target.d/finalise.d/80-fedora-atomic: line 29: DIB_IMAGE_ROOT_FS_UUID: unbound variable

The 'new' block level layer does currently not provide the UUID of the root partition. For other proposes the LABEL is used which is stored in DIB_ROOT_LABEL.

If you really need the UUID here, you need to patch
    diskimage-builder/diskimage_builder/block_device/blockdevice.py line 285ff
and add a block similar to root-label; adapt
    diskimage-builder/diskimage_builder/lib/disk-image-create
similar to line 309ff to store the result in a variable.