URL:
Reporter RHNID:
Section: - Start Processes in Containers
Language: en-US (English)
Workaround:

Description: In chapter 02, section 7 right after the podman exec -e ENVIRONMENT=dev -l env example we read the following:

After the env process finishes, the ENVIRONMENT variable is unset. To make the ENVIRONMENT variable persistent, stop the running container and add the -e ENVIRONMENT=dev option to the podman run command.

I my opinion students will understand that they can stop a container and modify it according to their needs. However, we know that podman run will either create a new container, or it will refuse to create one if another container with the same name exists.

Since the target audience of the course are developers and not system administrators, maybe we need to explain the difference or to change the text to something like the following:

After the env process finishes, the ENVIRONMENT variable is unset. To make the ENVIRONMENT variable persistent, stop and remove the running container and add the -e ENVIRONMENT=dev option to a new podman run command.