Docker and Docker-compose

Docker

Container-based deployments using Docker are recommended for single-node deployments. The container image for Partek Flow comes with all dependencies and third party utilities needed for all software features. This results in trivial initial deployments, upgrades, and maintenance.

Before proceeding, follow the Docker documentationarrow-up-right to install Docker.

Useful commands

docker ps

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

docker exec -it containername bash

This command will execute a shell in the container’s environment. This is useful for troubleshooting application or deployment issues.

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.“

Documentationarrow-up-right

Illumina support can assist customers with the creation of a docker-compose.yml file with all customer environment-specific configuration necessary to run Partek Flow on any server that meets our Minimum system requirementsarrow-up-right.

Below is an example docker-compose.yml file which after modification can be used to deploy Partek Flow. Such modifications are detailed in the description of important values following the example docker-compose.yml file.

Some important values in docker-compose.yml:

  • image: The container image tag. The value for $tag corresponds to the Partek Flow version. Please visit the Partek Flow Release Notes to find the latest version number and replace $tag with this value.

  • environment: Environment variables that configure additional Partek Flow features.

  • port: The exposed port used to access Partek Flow via a web browser. In this example http://localhost:8080/

  • mac_address: The mac_address needs to match the value for HOSTID in the provided Partek Flow license file. Note that the ":" character is required here, but may not be present in the HOSTID value.

  • volumes: This specifies the filesystem path on the server to be shared with the Partek Flow. All user data will be read and written to this path. Additional paths can be added. Where write access is required, e.g. the /home/flow mount, the path should be set to uid:gid 1000:1000.

Additional Assistance

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

Last updated