Embedded Registry(Hauler) start failed

[erpz22]

Problems:
The eib-embedded-registry.service failed to restart after boot to login, hauler store load failed with some tar.zst files in /opt/hauler/.
The error can find in the issue: hauler-dev/hauler#292

Steps to invest problem:

1. sha256sum to check with the file in /opt/hauler and original file in build folder under artefacts.
2. The file in ISO has same sha256sum value, but /opt/hauler is incorrect.
3. The incorrect file can not be load by hauler or uncompressed by zstd.

We use same ISO to install to another VM the file is correct and hauler started successfully.
The file size is very large(>12GB), I am not sure cp is safe enough to transfer large file size in 26-embedded-registry.sh.tpl.

[dbw7]

Hello, thank you for submitting this issue. I've had hauler work with large files before, also since it worked for you on another VM this might be a bit more difficult to track down. We plan to upgrade to Hauler v1.0.7 soon and hopefully this provides the fix for the issue.

[erpz22]

It works after replace to the newest hauler version v1.0.7, but that have to rebuild EIB images to replace the rpm installed one in EIB v1.0.2 will you provide the upgrade for all release EIB versions?

[jdob]

This will be addressed by #400

[dbw7]

Hello, we just upgraded to Hauler v1.0.7. If you’re building from source, your next build will automatically use the v1.0.7 RPM. If you’re only building SLE Micro 5.5 images and you’re not building from source (e.g. you’re using registry.opensuse.org) you’ll have to wait until the EIB v1.0.3 release of Edge.

If you’re using SL Micro 6.0 and you’re not building from source, you can use registry.opensuse.org/isv/suse/edge/edgeimagebuilder/containerfile-sp6/suse/edge-image-builder:1.1.0.rc2).
Please note that this is a release candidate and we’re looking forward to publishing an official release in September.

When you're able to test, can you please confirm that the upgrade solved your issue? Thank you very much!

[dbw7]

Closing this due to inactivity, if you run into any issues please feel free to reopen the ticket, thank you!