MENU
Is this a way to configure the Docker engine to use a registry without a trusted TLS certificate?
Solution. Set INSECURE_REGISTRY in the' /etc/docker/default' configuration file.
30 comments · newest first
FR
Francis
10 months ago
Yes, but only for local testing, right?
ST
Stevie
11 months ago
Wait, are we really okay with insecure registries?
AL
Alyce
11 months ago
Totally agree, it's a common workaround!
LI
Lizbeth
11 months ago
I thought that was a security risk though?
ME
Merlyn
11 months ago
That's correct, you can set INSECURE_REGISTRY.
JO
Johnathon
12 months ago
I’m pretty sure this is a valid method, but I wonder if there are any security implications we discussed in our last session.
BE
Bettina
12 months ago
I'm a bit confused. I thought there was another way to configure it, maybe through the daemon.json file instead?
ME
Melita
12 months ago
Yes, I believe setting INSECURE_REGISTRY in the '/etc/docker/default' file is correct. We practiced a similar question in class.
LE
Lenna
1 year ago
I think I remember something about configuring Docker with insecure registries, but I'm not entirely sure if it's done through that specific file.
TY
Tyra
1 year ago
Ah, I remember learning about this in class. Setting the INSECURE_REGISTRY option should do the trick. I've got a good feeling about this.
EM
Emily
1 year ago
Wait, what? I'm a bit confused about the whole TLS certificate thing. I'll need to review my notes on that.
MA
Mauricio
1 year ago
Okay, let's see. The key here is understanding how to configure the Docker engine to use a registry without a trusted TLS certificate. I think I can figure this out.
DO
Douglass
1 year ago
Hmm, I'm not totally sure about this. I'll need to think it through carefully.
MA
Margot
1 year ago
This seems pretty straightforward. I'm pretty confident I can handle this one.
JO
Joseph
1 year ago
Sure, if you want to leave the door open for all the docker daemons to come in and have a field day with your registry. What could possibly go wrong?
MA
Malinda
1 year ago
B) True, but it's important to weigh the risks and benefits before making that decision.
MO
Mozell
1 year ago
A) It's definitely a security risk, but sometimes it's necessary for testing or development purposes.
SC
Scarlet
1 year ago
B) No
TI
Timothy
1 year ago
A) Yes
TE
Tequila
1 year ago
Well, if you're running this in a controlled environment and know what you're doing, maybe. But in production? Nope, not a chance.
LA
Lawanda
1 year ago
Well, if you're running this in a controlled environment and know what you're doing, maybe. But in production? Nope, not a chance.
JI
Jimmie
1 year ago
B) No
LA
Lavonna
1 year ago
A) Yes
RY
Ryan
1 year ago
Setting INSECURE_REGISTRY? Sounds like a great way to invite the hackers to the party. No thank you!
ED
Edda
1 year ago
B) No
ID
Idella
1 year ago
A) Yes
KE
Keneth
1 year ago
Ah, the age-old question of Docker security. This is a classic case of 'Yeah, you can do it, but should you?'.
RA
Rasheeda
2 years ago
That makes sense, thanks for the clarification.
GR
Gracia
2 years ago
Yes, we can set INSECURE_REGISTRY in the configuration file.
RA
Rasheeda
2 years ago
Do you think we can configure Docker engine to use a registry without a trusted TLS certificate?