1. The Docker Container for Developer Edition is free, under a restricted license, and may be used for development and evaluation only.

2. It is geared towards the DataPower developer that wants to run DPOD on their development workstation, in the context of limited functionality.

3. It is deployed as a Docker container on a virtual machine or a laptop.

4. The Docker Container for Developer Edition is not entitled to IBM support.

Limitations

Docker installations are limited to:

• 3 monitored gateways.

• 1 monitored Cloud Agent, monitoring up to 3 monitored containerized gateways.

• 7 days, after which the container needs to be deleted and re-launched (unless the activation key is extended by generating an activation request key and sending it by email to your IBM representative).

Software Prerequisites

• RHEL/Rocky Linux/Ubuntu Desktop/MacOS operating system (Windows is not supported).

• Docker installed.

• Enable the following firewall rules:

  • Port 443 – Web/Admin Console access

  • Port 9022 – SSH access

  • Port 60000-60003 – Syslog agents (consume messages from the DataPower gateways)

  • Port 60020-60023 – WS-M agents (consume messages from the DataPower gateways)

  • For example:

    firewall-cmd --add-service=https --permanent firewall-cmd --add-port=9022/tcp --permanent firewall-cmd --add-port=60000-60003/tcp --permanent firewall-cmd --add-port=60020-60023/tcp --permanent firewall-cmd --reload

Hardware Prerequisites

• At least 6GB of disk space.

• At least 5GB of free memory.

• At least 2 Cores of Intel based CPUs.

Running the Docker Container

1. The DPOD Docker container uses volumes to store its data (configuration data, transactional data, log files, etc.).
   Create a directory for the volumes. Make sure to replace the following placeholders in the commands below:
   <DPOD Volumes Path>: The directory you’ve created for the volumes (e.g.: ${HOME}/dpod-volumes)

   DPOD_VOLUMES_PATH="<DPOD Volumes Path>" mkdir -p "${DPOD_VOLUMES_PATH}/data" "${DPOD_VOLUMES_PATH}/logs/httpd" "${DPOD_VOLUMES_PATH}/installs_logs" chmod -r 777 "${DPOD_VOLUMES_PATH}"

2. Use the docker pull command to pull the desired image from IBM container registry (icr.io). You may use a specific version (e.g. 1.0.22.1) or the latest version (using the latest tag). For example:

   docker pull icr.io/dpod/dpod-developer-edition:latest

3. Use the docker run command to create the DPOD Docker container. Make sure to replace the following placeholders in the command below:
   <DPOD Volumes Path>: The directory you’ve created for the volumes (e.g.: ${HOME}/dpod-volumes)
   <Host IP Address>: The IP Address of the host machine that runs the Docker containers

   The following environment variables can be used when invoking the command:

   • ACCEPT_LICENSE: (mandatory) Indication that the user accepts the EULA (End User License Agreement). For reviewing the license agreement see "Reviewing the license agreement" section below.

   • DPOD_EXT_HOST_IP: (mandatory) The Docker host IP address.

Access the DPOD container

• Web Console - Use the host machine IP address with the https protocol.

• SSH - Use the host machine IP address with port 9022.
  User is dpodadm with a default password of dpod.

Re-run Previously Created DPOD Docker Container

Review the License Agreement

For reviewing the license agreement, execute the following command when the container is running: