System Requirements for Polyspace Access

R2026b

There are two methods to deploy Polyspace^® Access™ on Docker^®:

Docker Compose — This is the recommended method for installing Polyspace Access. Docker Compose is a tool for defining and running multi-container Docker applications. You configure settings in an environment file (.env), and then start the deployment with docker compose up. Docker Compose manages the container lifecycle, networking between services, and restart behavior. See Install Polyspace Access using Docker Compose.
admin-docker-agent — A binary that provides a Cluster Admin web interface for installing, configuring, and starting the Polyspace Access Docker containers. admin-docker-agent will be removed in a future release. If you currently use admin-docker-agent, transition to Docker Compose. See Transition from admin-docker-agent to Docker Compose.

To install Polyspace Access components, use a currently supported version of the Docker API. To check the current minimum supported version of the Docker API, run the command docker version on your machine and view the Server API version entry. To force Docker to use the correct API version, set the environment variable DOCKER_API_VERSION to the minimum version or later. If you do not set this environment variable, Polyspace Access defaults to using Docker API version 1.24. For more information, see the Docker Engine API documentation.
Polyspace Access is compatible with Docker Engine on Linux^®.
To install Docker Engine on your machine, click one of these Docker supported Linux platforms and follow the installation instructions. The installation of Polyspace Access on a Linux platform is recommended.
Docker Engine is also available on other Linux distributions. For Docker on SUSE and Red Hat^®, see Docker EE on Linux distros.
Tip
You can use Kubernetes^® to deploy Polyspace Access. For more information, see Install Polyspace Access on Kubernetes.
The configuration of some Polyspace Access services requires the openssl toolkit to generate public and private keys. This toolkit is also required to configure Polyspace Access with HTTPS.
Polyspace Access licenses are network named user (NNU) licenses that require a license manager. Polyspace uses the FlexNet^® Publisher (FLEXlm^®) license manager. See Install License Manager on License Server.

To install Polyspace Access inside Linux virtual machines on Windows Server^® 2016 and 2019, you must:

You must also enable nested virtualization if you run Hyper-V inside of a Hyper-V VM.

Polyspace Access does not support installation on Windows Subsystem for Linux (WSL) and WSL2. See Polyspace Access Support on WSL.

The recommended minimum hardware configuration for Polyspace Access is:
- 4 cores
- 32 GB of RAM
- 500 GB of disk space
Frequent uploads might affect the performance of Polyspace Access. For instance, if you have a continuous integration process that regularly uploads more than 10 analysis results per hour, consider setting up multiple instances of Polyspace Access. For more information, contact MathWorks Technical Support.
See also Troubleshoot Issues with Database Connection Limits.
Data transfers between the server and client machines require a high-speed network connection. A gigabit network connection is recommended.
The Polyspace Access User Manager Dashboard does not support the Internet Explorer^® web browser.
Install Polyspace Access on the local drive of a physical machine.

Tip
You can use a relational database service (RDS) to host the Polyspace Access database. For more information, see External Database Settings.
- If you install on a network drive, the Polyspace Access database might run less efficiently and stored data might become corrupt.
- The installation of Polyspace Access on a virtual machine might result in up to a 50% overhead during I/O operations.
Do not install Polyspace Access inside a Docker container. Docker-in-Docker configurations can cause security profile and filesystem storage conflicts.

See Also