instruction: Create a Dockerfile for fundamentals
output: ```dockerfile
  from the
  build context before it's sent to the builder.If you use multiple Dockerfiles, you can use different ignore-files for each
  Dockerfile. You do so using a special naming convention for the ignore-files.
  Place your ignore-file in the same directory as the Dockerfile, and prefix the
  ignore-file with the name of the Dockerfile, as shown in the following example.
  
  .
  âââ index.ts
  âââ src/
  âââ docker
  âÂ Â  âââ build.Dockerfile
  âÂ Â  âââ build.Dockerfile.dockerignore
  âÂ Â  âââ lint.Dockerfile
  âÂ Â  âââ lint.Dockerfile.dockerignore
  âÂ Â  âââ test.Dockerfile
  âÂ Â  âââ test.Dockerfile.dockerignore
  âââ package.json
  âââ package-lock.jsonA Dockerfile-specific ignore-file takes precedence over the .dockerignore
  file at the root of the build context if both exist.SyntaxThe .dockerignore file is a newline-separated list of patterns similar to the
  file globs of Unix shells. Leading and trailing slashes in ignore patterns are
  disregarded. The following patterns all exclude a file or directory named bar
  in the subdirectory foo under the root of the build context:/foo/bar//foo/barfoo/bar/foo/barIf a line in .dockerignore file starts with # in column 1, then this line
  is considered as a comment and is ignored before interpreted by the CLI.
  
  #/this/is/a/commentIf you're interested in learning the precise details of the .dockerignore
  pattern matching logic, check out the
  moby/patternmatcher repository
  on GitHub, which contains the source code.MatchingThe following code snippet shows an example .dockerignore file.
  
  # comment
  */temp*
  */*/temp*
  temp?This file causes the following build behavior:RuleBehavior# commentIgnored.*/temp*Exclude files and directories whose names start with temp in any immediate subdirectory of the root. For example, the plain file /somedir/temporary.txt is excluded, as is the directory /somedir/temp.*/*/temp*Exclude files and directories starting with temp
  ```