Issue with Docker image from 21.4.414+

[bdwyertech]

Description

From container version 4.14.14+, test-kitchen seems to be broken. When it does a cookbook synchronization to the remote (kitchen-ec2), all files in the cookbooks are empty/blank within the kitchen/cookbooks folder on the remote. I have done a diff on the two containers and cannot figure it out. system packages are identical and the diff between workstation 21.4.413 and 414 does not seem to reflect anything which would break this.

Works great on all images up to and including chef/chefworkstation:21.4.413, but its broken on chef/chefworkstation:21.4.414+

# 21.4.414
[ec2-user@ip-10-1-2-3 ~]$ cat ~/kitchen/cookbooks/test/metadata.rb
[ec2-user@ip-10-1-2-3 ~]$

# 21.4.413
[ec2-user@ip-10-1-2-3 ~]$ cat ~/kitchen/cookbooks/test/metadata.rb
name 'test'
version '0.0.1'
depends 'myorg_aws_chef_server_app'

depends 'hostsfile'
depends 'ssl_certificate'

Diff with packaged deps

A container diff shows some difference in sizes of some of the compiled libraries.

container-diff diff chef/chefworkstation:21.4.413 chef/chefworkstation:21.4.414 --type=file

Chef Workstation Version

chef/chefworkstation:21.4.414+

Platform Version

Docker (Mac Big Sur)

[bdwyertech]

this is quite strange... berks vendor from within the container also generates empty files -- the only non-empty file is metadata.json

[bdwyertech]

The Berkshelf scratch directory looks good, it seems that the destination is what turns up empty. Quite strange. Stuck a couple sleep statements in, this is quite odd.

https://github.com/berkshelf/berkshelf/blob/6c7be8d7ff0a5f370490b47597e84ffbbaef3e88/lib/berkshelf/berksfile.rb#L688

This means that out of no where, this function is behaving differently... hmm...

https://github.com/berkshelf/berkshelf/blob/6c7be8d7ff0a5f370490b47597e84ffbbaef3e88/lib/berkshelf/file_syncer.rb#L56

It seems that FileUtils.cp is behaving erratically. Swapping to FileUtils.mv had the same effect. So strange...

[bdwyertech]

Related: docker/for-linux#1015

Adding --mount type=tmpfs,destination=/tmp to my docker launch config made all of this go away... This is very strange, why would two images have two different results.

[i5pranay93]

@bdwyertech hey, can you please send me some of the steps that results into this issue, I am not able to reproduce the same at my end.

[bdwyertech]

Issue has been resolved about a month ago as per my account team. My pipes work fine now on latest images.