Hi @jmeirow I’ve never run this under MacOS but since it’s running under docker, in theory it should work. My guess it that it’s a resource allocation issue of some kind. Is it possible that you are low on disk space or system RAM?
It is possible I’m running low on memory, as I’m running some VMs on this Mac as well. For the moment, i am actually going to move the mender-convert onto the VM (Ubuntu Server LTS 18.04) and see how that goes.
It’s so interesting you mention that. It’s worked for me dozens and dozens of times before on MacOS, and then it just stopped working. Weird. At least we both know we aren’t the only one
I really need to plow ahead so I’m building a new build machine on Linux (a VM).
My apologies for not updating this sooner. Not only does run without error on Linux (Ubuntu LTS 20.04), but it runs many times faster, literally. On my MacBook Pro, which is no slouch, it used to take 45-50 minutes. Now on Ubuntu, running in a VM on the same Mac, it runs in 5-7 minutes.
My Mac is running Mojave (10.14.6). I can’t speak to recent OS updates as it’s controlled by corporate. Disk Utility reports that the file system is APFS.
As to the speed, i have seen past reports of general performance issues between docker and MacOS running APFS file systems. I was also wondering if the APFS file system was also causing a problem for the sparse copy process in your error message as I have seen similar issues in other projects relating to ZFS.
I don’t have any macs to test only Linux machines, but if i did the next thing i would test would be to run docker on an HFS+ system (or external drive) not APFS, just to rule it in or out as a cause.