The command docker run --log-driver=splunk for every container at run time will configure a Docker container to export container logs to the logging solution. The reason is that the --log-driver option specifies the logging driver for the container, which determines how the container logs are handled1. The splunk logging driver is a plugin that sends container logs to HTTP Event Collector in Splunk Enterprise and Splunk Cloud2. To use the splunk logging driver, you also need to provide some additional options with the --log-opt flag, such as the Splunk token, URL, source, sourcetype, index, etc2. For example, to run a container with the splunk logging driver and send the logs to a Splunk instance with the URL https://splunk.example.com:8088 and the token 176fabb6-7811-4b3a-8ba0-4d49302e50f2, you can use:
docker run --log-driver=splunk --log-opt splunk-token=176fabb6-7811-4b3a-8ba0-4d49302e50f2 --log-opt splunk-url=https://splunk.example.com:8088 ...
This way, you can configure a Docker container to export container logs to Splunk, which is a centralized logging solution. Alternatively, you can also configure the splunk logging driver as the default logging driver for the Docker daemon by setting the log-driver and log-opts keys in the daemon.json file and restarting Docker3. This will apply the splunk logging driver to all containers unless overridden by the --log-driver option. References:
* Configure logging drivers
* Splunk logging driver
* Set the logging driver for the Docker daemon

Explanation
Using 'docker inspect http' does not enable you to view the list of historical tasks for this service. The docker inspect command shows low-level information about one or more objects, such as containers, images, networks, volumes, etc. It does not show information about services or tasks. To view the list of historical tasks for this service, you need to use 'docker service ps http'. References:
https://docs.docker.com/engine/reference/commandline/inspect/,
https://docs.docker.com/engine/reference/commandline/service_ps/

The command docker inspect http will not enable you to view the list of historical tasks for the service. The docker inspect command returns low-level information on Docker objects, such as containers, images, networks, or volumes1. It does not work on services, which are higher-level objects that define the desired state of a set of tasks2. To view the list of historical tasks for a service, you need to use the docker service ps command, which shows the current and previous states of each task, as well as the node, error, and ports3. Reference:
docker inspect | Docker Docs
Services | Docker Docs
docker service ps | Docker Docs

Explanation
n: = Using the DTR web UI to make all tags in the repository immutable is not a good way to prevent an image, such as 'nginx:latest', from being overwritten by another user with push access to the repository. This is because making all tags immutable would prevent any updates to the images in the repository, which may not be desirable for some use cases. For example, if a user wants to push a new version of 'nginx:latest' with a security patch, they would not be able to do so if the tag is immutable. A better way to prevent an image from being overwritten by another user is to use the DTR webUI to create a promotion policy that restricts who can push to a specific tag or repository1. Alternatively, the user can also use the DTR API to create a webhook that triggers a custom action when an image is pushed to a repository2. References:
* Prevent tags from being overwritten | Docker Docs
* Create webhooks | Docker Docs

The set of commands docker port inspect and docker container inspect will not identify the published port(s) for a container. The reason is that there is no such command as docker port inspect. The correct command to inspect the port mappings of a container is docker port1. The command docker container inspect can also show the port mappings of a container, but it will display a lot of other information as well, so it isnot as concise as docker port2. To identify the published port(s) for a container, you can use either of these commands:
docker port CONTAINER will list all the port mappings of the container1.
docker port CONTAINER PRIVATE_PORT will list only the port mapping of the specified private port of the container1.
docker container inspect --format=' { {.NetworkSettings.Ports}}' CONTAINER will list only the port mappings of the container in a JSON format23.
For example, if you have a container named web that publishes port 80 to port 8080 on the host, you can use any of these commands to identify the published port:
$ docker port web
80/tcp -> 0.0.0.0:8080
$ docker port web 80
0.0.0.0:8080
$ docker container inspect --format=' { {.NetworkSettings.Ports}}'web
map[80/tcp:[map[HostIp:0.0.0.0 HostPort:8080]]]
:
docker port
docker container inspect
How can I grab exposed port from inspecting docker container?