instruction: Create a Dockerfile for Node.js with production best practices
output: ```dockerfile
  from the wrong interface, causing incorrect proxy selection.For WindowsFixed a bug that prevented docker compose log to stream when running apps in WSL.Fixed a bug where Paketo buildpacks failed with Enhanced Container Isolation when Docker Desktop uses WSL.Fixed a bug where the WSL 2 integration would fail if WSL Version 1 distributions are installed.Fixed a bug that caused some CLI plugins update to fail if WSL distributions were enabled.Fixed a bug where Docker Desktop sign-in would hang when using a PAC file for proxy configuration, causing a blurred UI and blocking access.For LinuxThe Software Updates page in settings, now points to the latest available version available.4.38.02025-01-30Download Docker Desktop:Windows
  (checksum)Windows ARM Beta
  (checksum)Mac with Apple chip
  (checksum)Mac with Intel chip
  (checksum)Debian
  -
  RPM
  -
  Arch
  (checksum)NewInstalling Docker Desktop via the PKG installer is now generally available.Enforcing sign-in via configuration profiles is now generally available.Docker Compose, Docker Scout, the Docker CLI, and Ask Gordon can now be updated independently of Docker Desktop and without a full restart (Beta).The new
  update command has been added to the Docker Desktop CLI (Mac only).Bake is now generally available, with support for entitlements and composable attributes.You can now create
  multi-node Kubernetes clusters in Docker Desktop.Ask Gordon is more widely available. It is still in Beta.Upgradescontainerd v1.7.24Docker Buildx v0.20.1Docker Compose v2.32.4Docker Engine v27.5.1Docker Scout CLI v1.16.1Runc v1.2.2NVIDIA Container Toolkit v1.17.4Kubernetes v1.31.4Docker Debug v0.0.38Bug fixes and enhancementsFor all platformsFixed a bug where access tokens generated by the docker login web flow could not be refreshed by Docker Desktop.Fixed a bug where container creation via the Docker API using curl failed when
  Enhanced Container Isolation was enabled.Fixed a bug where the RAM policy was not refreshed after the refresh period had elapsed.Fixed a bug in Enhanced Container Isolation when mounting the Docker socket into a container, and then creating Docker containers with bind-mounts
  ```