instruction: Create a Dockerfile for fundamentals
output: ```dockerfile
  from the output of top that the specified ENTRYPOINT is not PID 1.If you then run docker stop test, the container will not exit cleanly - the
  stop command will be forced to send a SIGKILL after the timeout:
  
  $ docker exec -it test ps waux
  
  USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
  root 1 0.4 0.0 2612 604 pts/0 Ss+ 13:58 0:00 /bin/sh -c top -b --ignored-param2
  root 6 0.0 0.1 5956 3188 pts/0 S+ 13:58 0:00 top -b
  root 7 0.0 0.1 5884 2816 pts/1 Rs+ 13:58 0:00 ps waux
  
  $ /usr/bin/time docker stop test
  
  test
  real	0m 10.19s
  user	0m 0.04s
  sys	0m 0.03s
  Understand how CMD and ENTRYPOINT interactBoth CMD and ENTRYPOINT instructions define what command gets executed when running a container.
  There are few rules that describe their co-operation.Dockerfile should specify at least one of CMD or ENTRYPOINT commands.ENTRYPOINT should be defined when using the container as an executable.CMD should be used as a way of defining default arguments for an ENTRYPOINT command
  or for executing an ad-hoc command in a container.CMD will be overridden when running the container with alternative arguments.The table below shows what command is executed for different ENTRYPOINT / CMD combinations:No ENTRYPOINTENTRYPOINT exec_entry p1_entryENTRYPOINT ["exec_entry", "p1_entry"]No CMDerror, not allowed/bin/sh -c exec_entry p1_entryexec_entry p1_entryCMD ["exec_cmd", "p1_cmd"]exec_cmd p1_cmd/bin/sh -c exec_entry p1_entryexec_entry p1_entry exec_cmd p1_cmdCMD exec_cmd p1_cmd/bin/sh -c exec_cmd p1_cmd/bin/sh -c exec_entry p1_entryexec_entry p1_entry /bin/sh -c exec_cmd p1_cmd
  NoteIf CMD is defined
  ```