Chris Kim

The issue has been fixed in the following node.js versions: - [v18.20.0](https://nodejs.org/en/blog/release/v18.20.0) - [v20.12.0](https://nodejs.org/en/blog/release/v20.12.0) - [v21.7.1](https://nodejs.org/en/blog/release/v21.7.1) But for anyone unable to upgrade, you'll need to switch to a different unzipper...

This does look like a bug in nodejs, which can cause the `fstream` dependency to write out of order. Thanks @Fadorico for finding the change. I've created a nodejs issue...

The issue has been fixed in the following node.js versions: - [v18.20.0](https://nodejs.org/en/blog/release/v18.20.0) - [v20.12.0](https://nodejs.org/en/blog/release/v20.12.0) - [v21.7.1](https://nodejs.org/en/blog/release/v21.7.1) But for anyone unable to upgrade, you'll need to switch to a different unzipper...

@jmichalicek I believe I have the same issue but I cannot reproduce it using your example. I think downgrading Docker Desktop to `4.14.1` may help. Could you see if that...