Dormant Docker Working Group

[MikeMcC399]

The README > Dependent projects lists

https://github.com/nodejs/docker-node — administration delegated to the Docker Working Group

which is described in
https://github.com/nodejs/docker-node/blob/main/GOVERNANCE.md with its members listed in
https://github.com/nodejs/docker-node/blob/main/README.md#governance-and-current-members as

• Hans Kristian Flaatten (starefossen)
• Hugues Malphettes (hmalphettes)
• John Mitchell (jlmitch5)

I had previously raised the issue nodejs/docker-node#2278 about the outdated https://github.com/nodejs/docker-node/blob/main/GOVERNANCE.md document that received an acknowledgement from @Starefossen back in Sep 2025, without any further action being taken.

Is there any possibility for the TSC to review and possibly revive the Docker Working Group?

[mcollina]

We are already on it.

[MikeMcC399]

@mcollina

We are already on it.

I'm very glad to hear that!

I've also logged nodejs/docker-node#2363 due to recent delays in publishing Docker images because of musl delays and that seems like a topic for an active Docker Working Group to own, or at least get actively involved in.

[MikeMcC399]

I believe it would be helpful also if the TSC or their delegate Docker Working Group enabled a decision to be made on nodejs/docker-node#2264 involving the bundling of the unsupported Yarn v1 Classic package manager in Node.js Docker images.

I've proposed leaving Yarn v1 in current Node.js Docker images and stopping distribution in Node.js >=26 Docker images.

The Yarn team already reduced their involvement in v1 to the absolute minimum in 2020 when Yarn 2 was announced. They've just announced a preview for Yarn 6, based on another technology leap, so their statement that Yarn v1 is frozen and bugs will only be fixed in later versions needs to be taken seriously.