"tar_in: write error" while running genimage.fish

[live-2-code]

Hi Daniel, I am running the Makefile and encountered the following error, could you please assist?
Thank you.

make[1]: Leaving directory '/home/jianyepa/poplar/poplar-usbstick/poplar-linux'
tar --group 0 --owner 0 -C overlay -czf poplar-overlay.tar.gz .
guestfish -f genimage.fish
genimage.fish:18: libguestfs: error: tar_in: write error on directory: /:
genimage.fish:18: libguestfs: error: tar subprocess failed:
Makefile:81: recipe for target 'generate_image' failed
make: *** [generate_image] Error 1

[daniel-thompson]

On Sun, Jun 10, 2018 at 07:54:25PM -0700, ultimateyy wrote: Hi Daniel, I am running the Makefile and encountered the following error, could you please assist? Thank you.

Do you have a 128M file called poplar-boot.fat32 in the current directory (and permission to read for the user you are using to run make). If you have both of these things then it is likely the version of libguestfs you are using does not work correctly.

…

``` make[1]: Leaving directory '/home/jianyepa/poplar/poplar-usbstick/poplar-linux' tar --group 0 --owner 0 -C overlay -czf poplar-overlay.tar.gz . guestfish -f genimage.fish genimage.fish:18: libguestfs: error: tar_in: write error on directory: /: genimage.fish:18: libguestfs: error: tar subprocess failed: Makefile:81: recipe for target 'generate_image' failed make: *** [generate_image] Error 1 ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #4

[live-2-code]

@daniel-thompson , I just double confirmed that I have the 128M file. What version of libguestfs is required? I am having 1.36.13

[daniel-thompson]

On Mon, Jun 11, 2018 at 07:46:12PM -0700, Jeff wrote: @daniel-thompson , I just double confirmed that I have the 128M file.

... and permission is OK?

What version of libguestfs is required? I am having 1.36.13

I am not aware of any minimum version. However I said not working rather than too old (libguestfs is quite complex under the covers and I recall that some distros didn't set up the permissions quite right at one stage... unfortunately I don't really remember the details).

…

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #4 (comment)

[daniel-thompson]

BTW you do have plenty of disk space free, right? These are sparse images (meaning the size they appear to be is not what is allocated on the disk... that means that error reporting can be a bit weird if you run out of disk space).