instruction: Create a Dockerfile for fundamentals
output: ```dockerfile
  from a future release.Starting with Docker 20.10, experimental CLI features are enabled by default,
  and require no configuration to enable them.NotaryIf using your own notary server and a self-signed certificate or an internal
  Certificate Authority, you need to place the certificate at
  tls/<registry_url>/ca.crt in your Docker config directory.Alternatively you can trust the certificate globally by adding it to your system's
  list of root Certificate Authorities.OptionsOptionDefaultDescription--config/root/.dockerLocation of client config files-c, --contextName of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with docker context use)-D, --debugEnable debug mode-H, --hostDaemon socket to connect to-l, --log-levelinfoSet the logging level (debug, info, warn, error, fatal)--tlsUse TLS; implied by --tlsverify--tlscacert/root/.docker/ca.pemTrust certs signed only by this CA--tlscert/root/.docker/cert.pemPath to TLS certificate file--tlskey/root/.docker/key.pemPath to TLS key file--tlsverifyUse TLS and verify the remoteExamplesSpecify daemon host (-H, --host)You can use the -H, --host flag to specify a socket to use when you invoke
  a docker command. You can use the following protocols:SchemeDescriptionExampleunix://[<path>]Unix socket (Linux only)unix:///var/run/docker.socktcp://[<IP or host>[:port]]TCP connectiontcp://174.17.0.1:2376ssh://[username@]<IP or host>[:port]SSH connectionssh://user@192.168.64.5npipe://[<name>]Named pipe (Windows only)npipe:////./pipe/docker_engineIf you don't specify the -H flag, and you're not using a custom
  context,
  commands use the following default sockets:unix:///var/run/docker.sock on macOS and Linuxnpipe:////./pipe/docker_engine on WindowsTo achieve a similar effect without having to specify the -H flag for every
  command, you could also
  create a context,
  or alternatively, use the
  DOCKER_HOST environment variable.For more information about the -H flag, see
  Daemon socket option.Using TCP socketsThe following example shows how to invoke docker ps over TCP, to a remote
  daemon with IP address 174.17.0.1, listening on port 2376:
  
  $ docker -H tcp://174.17.0.1:2376 ps
  
  NoteBy convention, the Docker daemon uses port 2376 for secure TLS connections,
  and port 2375 for insecure, non-TLS connections.Using SSH socketsWhen you use SSH invoke a command on a remote daemon, the request gets forwarded
  to the /var/run/docker.sock Unix socket on the SSH host.
  
  $ docker -H ssh://user@192.168.64.5 ps
  You can optionally specify the location of the socket by appending a path
  component to the end of the SSH address.
  
  $ docker -H ssh://user@192.168.64.5/var/run/docker.sock ps
  SubcommandsCommandDescriptiondocker build (legacy builder)Build an image
  ```