February 13, 20206 yr Just clicked Update all and after pulling down the images, each Docker update is coming back with the following: Error: could not get decompression stream: fork/exec /usr/bin/unpigz: no such file or directory The attached logs seem to show something corresponding to network bridging, maybe connected to a NIC change I made recently? tower-diagnostics-20200213-1851.zip
February 14, 20206 yr I would say that this is related to the vmbackup plugin, since it's installing pigz Feb 1 12:41:41 Tower root: | Installing new package /boot/config/plugins/vmbackup/packages/pigz-2.3-x86_64-1_slonly.txz Remove the plugin and reboot and see if the problem continues.
February 14, 20206 yr @torch2k Hmmmm 🤔. Okay, just did some checking and it looks like docker looks for pigz by default. That said, when the plugin installs pigz, it does add /usr/bin/unpigz. Possibly your installation was corrupted somehow, since I just checked my dockers and two of them needed updated. I then ran Update All without issue. It seems like reinstalling the plugin could fix the issue for you... unless I'm missing something? -JTok
July 8, 20205 yr I have removed the VM Backup plugin - But I am now also getting this error when trying to update my docker images. any idea on a fix?
August 7, 20205 yr Another option instead of (though that works as well) - go over to nerd pack, and manually re-enable/re-install pigz (or just manually pull it from the slackware repo). I'm not super familiar with the plugin architecture, but if it allows you to do some checking/recording of packages it that it needed which were already available pre-install, that'd be cool... But then the nightmare of dependencies (i.e. what if they uninstall in a different order than install and leave behind components unintentionally) could be a freakin nightmare...
February 18, 20215 yr uninstall and reboot did the trick for me. also running 6.9.0-rc2, as the plugin was incompatible for me anyway.
Archived
This topic is now archived and is closed to further replies.