wp-env not being able to write in wp-content when mapped

[PanosSynetos]

Description

Disclaimer: Doesn't happen locally, happens when spinning up a site in GitHub Actions

Using the following mapping

	"mappings": {
		"./wp-content/uploads/images": "./tests/_support/docker/uploads"
	},

and spinning up a site in Github Actions, results in the uploads folder not being writable.

Unable to create file /var/www/html/wp-content/uploads/wc-logs/plugin-woocommerce-2024-04-09-83f15b8ae48838d072718368e84d6126.log because 
No such file or directory in /var/www/html/wp-admin/includes/class-wp-filesystem-direct.php on line 529

It also causes issues with the installation of WooCommerce and running imports through CLI, as

• WooCommerce cannot create the placeholder image
• The importer cannot import images

Step-by-step reproduction instructions

I can share links in private repositories ( WooCommerce Product Bundles, WooCommerce Composite Products) to check this out.

I discussed this with the team over at #woo-monorepo in Slack, but we couldn't figure out what might be causing this.

I'd like to add that this started when we updated to the latest wp-env

• from: npm i -g @wordpress/[email protected]
• to: npm i -g @wordpress/[email protected]

so I assume that somewhere in between changed.

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes