Is this a way to configure the Docker engine to use a registry without a trusted TLS certificate? Pass the ‘--insecure registry’ flag to the daemon at run time.
A. Yes
Explanation:
Passing the --insecure-registry flag to the Docker daemon at runtime is a valid way to configure the Docker engine to use a registry without a trusted TLS certificate.
Details:
The --insecure-registry flag tells the Docker daemon to allow communication with a specific registry without verifying its TLS certificate. However, this flag must be passed when starting the Docker daemon.
Example:
If starting the Docker daemon manually, you can use:
dockerd --insecure-registry <registry-address>:<port>
Using the --insecure-registry flag when starting the Docker daemon is a valid and supported method to configure Docker to accept an untrusted registry.
No, you cannot pass the --insecure-registry flag to the Docker daemon at runtime. This is a configuration option that must be set before starting the Docker daemon. Any changes to this setting require restarting the Docker service.
I think the answer is B. "--insecure" is not a valid flag.
upvoted 1 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Raji82
1 month, 1 week agobadalchavan11
2 months, 1 week ago__rajan__
2 months, 3 weeks agoLavaPup
3 months, 3 weeks agovladcp
6 months, 1 week ago