The sequence of steps will not completely delete an image from disk in the Docker Trusted Registry. Deleting an image and deleting an image repository from the Docker Trusted Registry will only remove the references to the image, but not the actual image data on the disk1. To completely delete an image from disk, you need to run the garbage collection command on the registry server, which will delete any unreferenced blobs2. The garbage collection command is bin/registry garbage-collect /path/to/config.yml3. References: Deleting an image), Garbage collection), Running garbage collection)

Explanation
The answer depends on whether you want to access the container from the host's network or from other containers on the same network. EXPOSE and --publish have different effects on the container's port visibility. References: Docker run reference, Dockerfile reference, Docker networking overview

The solution given is not a valid way to provide a configuration file to a container at runtime using Kubernetes tools and steps. The reason is that there is no such key as .spec.containers.configMounts in the PodSpec. The correct key to use is .spec.containers.volumeMounts, which specifies the volumes to mount into the container's filesystem1. To use a ConfigMap as a volume source, one needs to create a ConfigMap object that contains the configuration file as a key-value pair, and then reference it in the .spec.volumes section of the PodSpec2. A ConfigMap is a Kubernetes API object that lets you store configuration data for other objects to use3. For example, to provide a nginx.conf file to a nginx container, one can do the following steps:
* Create a ConfigMap from the nginx.conf file:
kubectl create configmap nginx-config --from-file=nginx.conf
* Create a Pod that mounts the ConfigMap as a volume and uses it as the configuration file for the nginx container:
apiVersion: v1
kind: Pod
metadata:
name: nginx-pod
spec:
containers:
- name: nginx
image: nginx
volumeMounts:
- name: config-volume
mountPath: /etc/nginx/nginx.conf
subPath: nginx.conf
volumes:
- name: config-volume
configMap:
name: nginx-config
References:
* Configure a Pod to Use a Volume for Storage | Kubernetes
* Configure a Pod to Use a ConfigMap | Kubernetes
* ConfigMaps | Kubernetes

Explanation
= Setting and exporting the IGNORE_TLS environment variable on the command line is not a way to configure the Docker engine to use a registry without a trusted TLS certificate. This environment variable is not recognized by Docker and has no effect on theTLS verification process1. To use a registry without a trusted TLS certificate, you need to either add the certificate to the system or Docker-specific trust store, or configure the Docker daemon to allow insecure registries23. References:
* Environment variables | Docker Docs
* Verify repository client with certificates | Docker Docs
* Test an insecure registry | Docker Docs