DCA · Question #64
Is this a way to configure the Docker engine to use a registry without a trusted TLS certificate? Solution: Pass the '--insecure-registry' flag to the daemon at run time.
The correct answer is A. Yes. Passing the --insecure-registry flag to the Docker daemon at runtime is a valid way to configure it to use a registry without a trusted TLS certificate.
Question
Is this a way to configure the Docker engine to use a registry without a trusted TLS certificate? Solution: Pass the '--insecure-registry' flag to the daemon at run time.
Options
- AYes
- BNo
How the community answered
(17 responses)- A94% (16)
- B6% (1)
Why each option
Passing the `--insecure-registry` flag to the Docker daemon at runtime is a valid way to configure it to use a registry without a trusted TLS certificate.
The `--insecure-registry` daemon flag explicitly configures the Docker engine to bypass TLS certificate validation for the specified registry. This allows Docker to communicate with registries that use self-signed certificates or no encryption, which is often necessary for private development registries or testing environments.
Docker provides mechanisms to interact with registries that do not present trusted TLS certificates, and the `--insecure-registry` flag is the specific daemon configuration option for this purpose.
Concept tested: Docker insecure registry configuration
Source: https://docs.docker.com/engine/reference/commandline/dockerd/#options
Topics
Community Discussion
No community discussion yet for this question.