-
Bug
-
Resolution: Done
-
Minor
-
DO188 - RHOSCP4.14-en-1-20240307
-
None
-
False
-
-
False
-
2
-
ROLE
-
-
-
en-US (English)
-
AppDev Sprint 27-Jun
Please fill in the following information:
URL: | https://role.rhu.redhat.com/rol-rhu/app/courses/do188-4.14/pages/ch02s04 |
Reporter RHNID: | yuvaraj-rhls |
Section Title: | Quiz: Container Networking Basics |
Issue description
Description: In Chapter 2 Section 4, the 6th question asks whether the default podman network could replace one of the networks in this configuration. The material on the previous page suggests this is not possible, and the solution of overwriting the network to enable DNS is not mentioned.
Replied to user on the same snow request :-
< I checked on the 6th quiz question and I see that the solution provided <Yes, but the podman network needs to be overwritten to enable DNS.> matches the topic on the previous section. Here overwritten means you will have to replace it with the custom configuration so that DNS can be enabled. >
However user added :-
<This is still confusing me. I do not see any reference to 'overriding the
default network' in order to enable DNS. The course suggests creating a new
network instead of using the default if you need DNS.
I think 'creating a Podman network' is not the same as 'overriding' the
default network, as it adds an additional bridge, rather than overwriting
anything.
I believe the correct answer should be:
D No, because the default podman network cannot provide DNS.
The answer in D is explicitly stated in the previous topic.
From the topic " When you use the default Podman network, the domain name
system (DNS) for other containers in that network is disabled. To enable
DNS resolution between containers, create a Podman network and connect your
containers to that network." >