= The sequence of steps will not completely delete an image from disk in the Docker Trusted Registry.
Deleting the image and removing permissions to the repository will only remove the image from the registry's user interface and prevent unauthorized access to it. However, the image data will still remain on the registry's storage backend until garbage collection is performed1. Garbage collection is a process that removes unused blobs (layers) from the registry's storage2. To run garbage collection, the registry must be stopped and the command bin/registry garbage-collect /etc/docker/registry/config.yml must be executed3. Alternatively, the registry can be configured to run garbage collection automatically at regular intervals4. References:
* Deleting images | Docker Documentation
* Garbage collection | Docker Documentation
* How to delete images from a private docker registry? | Stack Overflow
* Automating garbage collection | Docker Documentation

The command docker system events --filter splunk will not configure a Docker container to export container logs to the logging solution. The command docker system events will display real-time events from the Docker daemon, such as container creation, start, stop, etc. The --filter option will filter the events by various criteria, such as type, label, name, etc. However, there is no filter for splunk, and even if there was, it would only show the events related to Splunk, not the container logs. To configure a Docker container to export container logs to Splunk, you need to use the Splunk logging driver, which is a plugin that sends container logs to HTTP Event Collector in Splunk Enterprise and Splunk Cloud. You can use the --log-driver and --log-opt options when creating or running a container to specify the Splunk logging driver and its options, such as the Splunk token, URL, source, sourcetype, index, etc. Alternatively, you can 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 Docker. References:
* docker system events
* Splunk logging driver
* How to send Docker containers logs to Splunk?

= Creating images that contain the specific configuration for every environment is not a way to provision configuration to containers at runtime. This approach violates the principle of separating application code from configuration, and makes the images less portable and reusable across different environments1. It also increases the maintenance overhead and the risk of configuration drift, as any change in the configuration would require rebuilding and redeploying the images2. To provision configuration to containers at runtime, you should use a different mechanism, such as environment variables, command-line arguments, or config maps345. Reference:
Configuration management with Containers | Kubernetes
Environment variables in Compose | Docker Docs
Override the default command | Docker Docs
Configuration management with Containers | Kubernetes

= Mirroring the engineering/api repository to one of the user's own private repositories will not grant them read/write access to the original repository. Mirroring is a feature that allows users to automatically sync images from one repository to another, either within the same DTR or across different DTRs. Mirroring does not affect the permissions or roles of the users or teams associated with the source or destination repositories.
To grant a user read/write access to the engineering/api repository, the user needs to be added to a team that has the appropriate role for that repository, or the repository needs to be configured with the appropriate visibility and access settings. References:
* Mirror repositories
* Manage access to repositories
* Manage teams

Explanation
This does not configure a Docker container to export container logs to the logging solution. The docker system events command shows information about real-time events in the Docker daemon. The --filter flag allows you to filter the output by various criteria, such as type, action, image, container, etc. However, splunk is not a valid filter value and will cause an error. To configure a Docker container to export container logs to the logging solution, you need to use the --log-driver and --log-opt flags when creating or running the container.
These flags allow you to specify which logging driver and options to use for the container. For example, to use Splunk as the logging driver, you can use --log-driver splunk and provide the Splunk URL, token, and other options using --log-opt. References: https://docs.docker.com/engine/reference/commandline/system_events/,
https://docs.docker.com/config/containers/logging/configure/,
https://docs.docker.com/config/containers/logging/splunk/