twoliter
twoliter copied to clipboard
tar: file changed as we read it
I've noticed occasional build failures with VMware variants because of errors like this:
tar: bottlerocket-vmware-k8s-1.31-x86_64-1.34.0-f3d88ccc6.vmdk: file changed as we read it
I'm pretty sure this happens if we get a sequence like this:
-
rpm2img,rpm2kmodkit,rpm2migrationsall start -
rpm2imgcreates the VMDK file -
rpm2kmodkitorrpm2migrationsfinishes -
rpm2imgstarts the OVA creation - the recursive chown of everything in
/outputstarts -
rpm2imgobserves the VMDK change fromroot:roottobuilder:builder- error!
In theory any of these stages could finish first, then disrupt a tar operation in progress in one of the other stages when it runs chown.