Explanation
Better logical separation of Dockerfile instructions for increased readability is not an advantage of multi-stage builds. Multi-stage builds are a feature that allows you to use multiple FROM statements in your Dockerfile.
Each FROM statement begins a new stage of the build. You can selectively copy artifacts from one stage to another, leaving behind everything you don't want in the final image. The main advantage of multi-stage builds is that they allow you to reduce the size of your final image by only including the essential components and dependencies. Another advantage of multi-stage builds is that they allow you to optimize the build cache by grouping similar instructions in each stage. Better logical separation of Dockerfile instructions for increased readability is not an inherent advantage of multi-stage builds, as it depends on how you write and organize your Dockerfile. References: https://docs.docker.com/develop/develop-images/multistage-build/,
https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#use-multi-stage-builds

Explanation
Kubernetes does not automatically trigger a user-defined script to attempt to fix the unhealthy container, because Kubernetes does not have such a feature. According to the official documentation, Kubernetes only supports three types of probes: exec, httpGet, and tcpSocket, and none of them can execute arbitrary scripts.
References:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-li

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. The IGNORE_TLS environment variable is not recognized by Docker and has no effect on its behavior. To configure the Docker engine to use a registry without a trusted TLS certificate, you need to either set INSECURE_REGISTRY in the /etc/docker/default configuration file or add --insecure-registry flag to the dockerd command. References:
https://docs.docker.com/registry/insecure/,
https://docs.docker.com/engine/reference/commandline/dockerd/#insecure-registries