URL:
Reporter RHNID:
Section: -
Language: en-US (English)||||||||
Workaround: To solve this problem, instructors need to know how to work with

-compose and where the definition file is located at (/home/student/.venv/labs/lib/python3.6/site-packages/ad221/common/files and look at the respective GE directory) and run podman-compose up to start them up. Eventually some containers might be hanging and it requires you to run podman-compose down in the same directory.
If even with that the containers aren't gone, you need to run podman rm -r -f or podman pod rm -r -f

Description: 24879

Description: All labs that use containers to run the services used to test apps have a common issue. If a student needs to boot the machine due to some misbehavior of the ROL env, the containers will be killed and when the student decides to test the lab it will fail as the service was killed as part of the reboot. 

To solve this problem, instructors need to know how to work with {podman,docker}-compose and where the definition file is located at (/home/student/.venv/labs/lib/python3.6/site-packages/ad221/common/files and look at the respective GE directory) and run podman-compose up to start them up. Eventually some containers might be hanging and it requires you to run podman-compose down in the same directory.

An alternative approach would be, run the lab start again. However, the lab start will overwrite anything that students have changed and delete all the updates done.

To minimize pain, I suggest to either create a verb like start-containers and stop-containers on each of these GEs that uses containers.