-
Bug
-
Resolution: Unresolved
-
Minor
-
DO188 - RHOSCP4.14-en-3-20241023
-
None
-
False
-
-
False
-
-
-
en-US (English)
Please fill in the following information:
URL: | https://role.rhu.redhat.com/rol-rhu/app/courses/do188-4.14/pages/ch09s02 |
Reporter RHNID: | shasingh01 |
Section Title: | Lab: Comprehensive Reviewh5. |
Issue description
I think it makes more sense for the instruction "Use the --ulimit
nofile=65535:65535 as a build parameter to avoid a build error." to be
included under the section "Create a container image for the Beeper UI that
matches the following criteria", since it's part of the image creation
steps, rather than under "Create a container for the Beeper UI that matches
the following criteria", which is the instruction for creating a container
from the built image. When I was running through the lab initially it was
confusing for me why I was getting a nofile error during the build steps,
and I didn't realize until I moved on to the next section that the ulimit
flag should be used to build the image and not when creating the
container. However
it's possible I've misunderstood and the instructions are correct as
written.
Steps to reproduce:
Workaround:
Expected result: