code: func dispatchEntrypoint(d dispatchRequest, c *instructions.EntrypointCommand) error {
  	runConfig := d.state.runConfig
  	cmd, argsEscaped := resolveCmdLine(c.ShellDependantCmdLine, runConfig, d.state.operatingSystem, c.Name(), c.String())
  
  	// This warning is a little more complex than in dispatchCmd(), as the Windows base images (similar
  	// universally to almost every Linux image out there) have a single .Cmd field populated so that
  	// `docker run --rm image` starts the default shell which would typically be sh on Linux,
  	// or cmd on Windows. The catch to this is that if a dockerfile had `CMD ["c:\\windows\\system32\\cmd.exe"]`,
  	// we wouldn't be able to tell the difference. However, that would be highly unlikely, and besides, this
  	// is only trying to give a helpful warning of possibly unexpected results.
  	if d.state.operatingSystem == "windows" &&
  		d.state.runConfig.ArgsEscaped != argsEscaped &&
  		((len(runConfig.Cmd) == 1 && strings.ToLower(runConfig.Cmd[0]) != `c:\windows\system32\cmd.exe` && len(runConfig.Shell) == 0) || (len(runConfig.Cmd) > 1)) {
  		fmt.Fprintf(d.builder.Stderr, " ---> [Warning] Shell-form CMD and exec-form ENTRYPOINT may have unexpected results\n")
  	}
  
  	runConfig.Entrypoint = cmd
  	runConfig.ArgsEscaped = argsEscaped
  	if !d.state.cmdSet {
  		runConfig.Cmd = nil
  	}
  
  	return d.builder.commit(d.state, fmt.Sprintf("ENTRYPOINT %q", runConfig.Entrypoint))
  }
docs: // ENTRYPOINT /usr/sbin/nginx
  //
  // Set the entrypoint to /usr/sbin/nginx. Will accept the CMD as the arguments
  // to /usr/sbin/nginx. Uses the default shell if not in JSON format.
  //
  // Handles command processing similar to CMD and RUN, only req.runConfig.Entrypoint
  // is initialized at newBuilder time instead of through argument parsing.
  //