Docker and Docker-compose

Docker

Docker can be used along Partek Flow to deploy an easy to maintain environment which will not have dependency issues and will be easy to relocate among different servers if needed.

One can follow the Docker documentation to install Docker.

Useful commands

docker ps

This command will output the details of the currently running containers including port forwarding, container name/id, and uptime.

docker exec

This command will allow us to enter the running container’s environment to troubleshoot any issues we might have with the container.

Docker-compose

“Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration.“

Documentation

Partek support will work with the customer to customize a docker-compose file that will have all the configuration necessary to run Partek Flow on any machine that meets our Minimum system requirements.

Below it is an example docker-compose.yml file which can be used to deploy Partek Flow.

services:
  flowheadnode:
    restart: unless-stopped
    image: public.ecr.aws/partek-flow/rtw:latest
    hostname: flowheadnode
    environment:
      # Set license location. Can be a server ex. @lic-test.example.com or /home/flow/.partekflow/license/Partek.lic
      - PARTEKLM_LICENSE_FILE=/home/flow/.partekflow/license/Partek.lic
    ports:
      - "8080:8080"
    # The MAC must match what is in the license file or defined on the license server. Please change this.
    networks:
      flexlm:
        mac_address: aa:bb:cc:dd:ee:ff
    # The internal path must be /home/flow
    volumes:
      # This uses an external path for the Flow data. The 'flow' user inside the container must be able to read and write to this directory.
      - /home/flow:/home/flow
networks:
  flexlm:

These are some of the important tags shown above:

  • restart: whether you want the container to be restarted automatically upon failure or system restart.

  • image: the container image tag. It is recommended to run the latest version of Partek Flow. If you need any specific versions of Partek Flow please visit here.

  • environment: here we set up any environment variables to be run along the container.

  • port: the exposed port used to access Partek Flow via a web browser.

  • mac_address: this needs to match your license file.

  • volumes: in this section we specify the folder on the server to be shared with the container, this way we can better persist and access the files we create and use in the container.

Additional Assistance

If you need additional assistance, please visit our support page to submit a help ticket or find phone numbers for regional support.

Last updated