instruction: Create a Dockerfile for Node.js with production best practices
output: ```dockerfile
  from using so much of any resource that this over-use affects other teams.You should also consider what access you grant to that namespace:
  full write access to a namespace allows someone with that access to remove any
  resource, including a configured ResourceQuota.My container is terminatedYour container might get terminated because it is resource-starved. To check
  whether a container is being killed because it is hitting a resource limit, call
  kubectl describe pod on the Pod of interest:kubectl describe pod simmemleak-hra99
  The output is similar to:Name: simmemleak-hra99
  Namespace: default
  Image(s): saadali/simmemleak
  Node: kubernetes-node-tf0f/10.240.216.66
  Labels: name=simmemleak
  Status: Running
  Reason:
  Message:
  IP: 10.244.2.75
  Containers:
   simmemleak:
   Image: saadali/simmemleak:latest
   Limits:
   cpu: 100m
   memory: 50Mi
   State: Running
   Started: Tue, 07 Jul 2019 12:54:41 -0700
   Last State: Terminated
   Reason: OOMKilled
   Exit Code: 137
   Started: Fri, 07 Jul 2019 12:54:30 -0700
   Finished: Fri, 07 Jul 2019 12:54:33 -0700
   Ready: False
   Restart Count: 5
  Conditions:
   Type Status
   Ready False
  Events:
   Type Reason Age
  ```