See these pages for more information:
Docker CLI: docker run (run a command in a new container)
https://docs.docker.com/engine/containers/run/

The 'docker run' command has the following syntax:
$ docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
Note that docker container run is equivalent to docker run

The command 'docker run', first creates the container (from the specified image) and then starts it.

Let's run the nginx image:
$ docker run --rm -d nginx:1.19.1 02404a9bc24bc3f7222035a9b7eaa698557bb53f660222858c7f590556762730
The option '-d' (--detach) run the container in background and print container ID.

The option '--rm' tells Docker to automatically remove the container when it exits.

Let's verify that nginx is up and running:
$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 02404a9bc24b nginx:1.19.1 "/docker-entrypoint.…" 2 minutes ago Up 2 minutes 80/tcp vibrant_mose
You can notice that the name of the container (vibrant_mose) is a random name generated by Docker.
To give a custom name to the container, you can use the option '--name'.

Note that the container's port (80) is not published to the Docker's host.
To publish an exposed container's port and map it to a host's port, you can use the option '-p HOST_PORT:CONTAINER_PORT'.
You can also use the option '-P' to publish all exposed ports to random ports in the Docker's host.

Let's use the two options ('-p', '--name') and run again the nginx image:
$ docker run --rm -d -p 8080:80 --name "nginx-1.19.1" nginx:1.19.1 9fbfa15209c6de85b955b75531e9a464d123ea0a39d95799e9817b9880b4b240
Let's verify that both the specified port (the container port 80 is mapped to the Docker host port 8080) and the name were used:
$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9fbfa15209c6 nginx:1.19.1 "/docker-entrypoint.…" 2 minutes ago Up 2 minutes 0.0.0.0:8080->80/tcp nginx-1.19.1
You can use the option '--no-trunc' of the 'ps' command to print the full container ID and the command used to start the nginx process.
$ docker ps --no-trunc CONTAINER ID IMAGE COMMAND PORTS NAMES 9fbfa15209c6de85b955b75531e9a464d123ea0a39d95799e9817b9880b4b240 nginx:1.19.1 "/docker-entrypoint.sh nginx -g 'daemon off;'" 0.0.0.0:8080->80/tcp nginx-1.19.1
Let's access nginx at the published port 8080:

The "docker run" command has two options that allow you to set environment variables for your containers:
-e, --env NAME=VALUE Set environment variables --env-file file Read in a file of environment variables
Let's try the option "-e" ("--env"):
$ docker run -e my_env_var_1="my env var 1 value" -e my_env_var_2="my env var 2 value" ubuntu:latest /bin/bash -c "env | grep my_env_var_" my_env_var_1=my env var 1 value my_env_var_2=my env var 2 value
The two environment variables were set properly. The applications running inside the container can use them as they would in a regular deployment in a native host.

In some cases, setting environment variables using the option "-e" can be cumbersome especially if we want to set many of them. Optionally, you can group all the environment variables in a property file and use the option "--env-file" to pass the file to "docker run" command.

Let's create a property file:
$ vi env-file-1 my_env_var_1=my env var 1 value my_env_var_2=my env var 2 value my_env_var_3=my env var 3 value
Let's use the option "--env-file":
$ docker run --env-file env-file-1 ubuntu:latest /bin/bash -c "env | grep my_env_var_" my_env_var_1=my env var 1 value my_env_var_2=my env var 2 value my_env_var_3=my env var 3 value