instruction: Create a Dockerfile for Alpine Linux with production best practices
output: ```dockerfile
  from an image for its filesystem.
  Each container also gets its own "scratch space" to create/update/remove files. Any
  changes won't be seen in another container, even if they're using the same image.See this in practiceTo see this in action, you're going to start two containers. In one container,
  you'll create a file. In the other container, you'll check whether that same
  file exists.Start an Alpine container and create a new file in it.
  
  $ docker run --rm alpine touch greeting.txt
  
  TipAny commands you specify after the image name (in this case, alpine)
  are executed inside the container. In this case, the command touch greeting.txt puts a file named greeting.txt on the container's filesystem.Run a new Alpine container and use the stat command to check whether the file exists.
  
  $ docker run --rm alpine stat greeting.txt
  You should see output similar to the following that indicates the file does not exist in the new container.
  
  stat: can't stat 'greeting.txt': No such file or directory
  The greeting.txt file created by the first container did not exist in the
  second container. That is because the writeable "top layer" of each container
  is isolated. Even though both containers shared the same underlying layers that
  make up the base image, the writable layer is unique to each container.Container volumesWith the previous experiment, you saw that each container starts
  ```