= This is not a way to configure the Docker engine to use a registry without a trusted TLS certificate. There is no such option as IGNORE_TLS in the daemon.json configuration file. The daemon.json file is used to configure various aspects of the Docker engine, such as logging, storage, networking, and security1. To use a registry without a trusted TLS certificate, you need to either add the certificate to the trusted root certificates of the system, or configure the Docker engine to allow insecure registries2. To add the certificate to the trusted root certificates, you need to copy the certificate file to the /etc/docker/certs.d/<registry-hostname>/ directory on every Docker host2. To configure the Docker engine to allow insecure registries, you need to add the registry hostname or IP address to the "insecure-registries" array in the daemon.json file3. For example:
{ "insecure-registries" : ["myregistry.example.com:5000"] }
Note that using insecure registries is not recommended, as it exposes you to potential man-in-the-middle attacks and data corruption3. You should always use a registry with a trusted TLS certificate, or use Docker Content Trust to sign and verify your images4. References:
* Daemon configuration file | Docker Docs
* Verify repository client with certificates | Docker Docs
* Test an insecure registry | Docker Docs
* Content trust in Docker | Docker Docs

Explanation
= Multi-stage builds allow you to use multiple FROM statements in your Dockerfile, each starting a new stage of the build1. This can help you achieve better logical separation of Dockerfile instructions for increased readability, as well as other benefits such as smaller image size, faster build time, and reduced security risks23.
By separating your Dockerfile into different stages, you can organize your instructions by their purpose, such as building, testing, or deploying your application. You can also copy only the artifacts you need from one stage to another, leaving behind the unnecessary dependencies or tools1. This can make your Dockerfile easier to read and maintain, as well as improve the performance and security of your final image. References:
* Multi-stage builds | Docker Docs
* What Are Multi-Stage Docker Builds? - How-To Geek
* Multi-stage | Docker Docs

Explanation
pid is not a Linux kernel namespace that is disabled by default and must be enabled at Docker engine runtime to be used. pid is a Linux kernel namespace that provides process isolation for containers. It ensures that processes in one container cannot see or signal processes in another container or on the host system. pid is enabled by default for Docker containers and does not require any special flag or option to be used. However, you can disable pid isolation for a container by using --pid host option when creating or running a container.
This option connects the container to the host's pid namespace and allows the container to see and signal processes on the host system. References: https://docs.docker.com/engine/reference/run/#pid-settings-pid,
https://en.wikipedia.org/wiki/Linux_namespaces#Process_ID_(pid)