Ensuring that the containers-based services are automatically started after system startup

Follow the instructions to ensure that containers-based services are automatically started after system startup.

About this task

If you use Docker and Docker Compose to manage software containers, the containers-based services are automatically started at system boot when the following conditions are met:

The docker daemon is enabled in systemd to automatically start at system boot.
All Z Data Analytics Platform containers are set to restart: always in the Docker Compose YAML files. This is the default setting and must not be changed unless instructed by IBM® Support.
The docker daemon is allowed to control the shutdown of Z Data Analytics platform. If you run ./bin/dockerManageZoa.sh down before rebooting the system, the Z Data Analytics Platform will not automatically start when the system boots. If you allow the docker daemon to shut down the Z Data Analytics Platform containers as the system reboots, then the containers will automatically restart.

For more information about how to launch a daemon at system boot time, see the documentation of your Linux® distribution.

Note: Podman does not support automatic restart of OCI containers at system startup. To automatically start the Z Data Analytics Platform at system startup if you use Podman, you must invoke podmanManageZoa.sh either through a cron job or through a custom systemd service definition.