instruction: Create a Dockerfile for Node.js with production best practices
output: ```dockerfile
  from the runtime,
  and ignores the cgroupDriver setting within the kubelet configuration.Caution:Changing the cgroup driver of a Node that has joined a cluster is a sensitive operation.
  If the kubelet has created Pods using the semantics of one cgroup driver, changing the container
  runtime to another cgroup driver can cause errors when trying to re-create the Pod sandbox
  for such existing Pods. Restarting the kubelet may not solve such errors.If you have automation that makes it feasible, replace the node with another using the updated
  configuration, or reinstall it using automation.Migrating to the systemd driver in kubeadm managed clustersIf you wish to migrate to the systemd cgroup driver in existing kubeadm managed clusters,
  follow configuring a cgroup driver.CRI version supportYour container runtime must support at least v1alpha2 of the container runtime interface.Kubernetes starting v1.26
  only works with v1 of the CRI API. Earlier versions default
  to v1 version, however if a container runtime does not support the v1 API, the kubelet falls back to
  using the (deprecated) v1alpha2 API instead.Container runtimesNote: This section links to third party projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for these projects, which are listed alphabetically. To add a project to this list, read the content guide before submitting a change. More information.containerdThis section outlines the necessary steps to use containerd as CRI runtime.To install containerd on your system, follow the instructions on
  getting started with containerd.
  Return to this step once you've created a valid config.toml configuration file.LinuxWindowsYou can find this file under the path /etc/containerd/config.toml.You can find this file under the path C:\Program Files\containerd\config.toml.On Linux the default CRI socket for containerd is /run/containerd/containerd.sock.
  On Windows the default CRI endpoint is npipe://./pipe/containerd-containerd.Configuring the systemd cgroup driverTo use the systemd cgroup driver in /etc/containerd/config.toml with runc,
  set the following config based on your Containerd versionContainerd versions 1.x:[plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
   ...
   [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
   SystemdCgroup = true
  Containerd versions 2.x:[plugins.'io.containerd.cri.v1.runtime'.containerd.runtimes.runc]
   ...
   [plugins.'io.containerd.cri.v1.runtime'.containerd.runtimes.runc.options]
   SystemdCgroup = true
  The systemd cgroup driver is recommended if you use cgroup v2.Note:If you installed containerd
  ```