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.
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.
I think the answer is B. "--insecure" is not a valid flag.
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.
Using the --insecure-registry flag when starting the Docker daemon is a valid and supported method to configure Docker to accept an untrusted registry.
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>
It's A ish... should be --insecure-registry not --insecure registry