Requirements

This page lists the requirements to run beLow on a Windows environment

Minimum hardware requirements to run the full solution locally:

Full solution

• 4-core x86-64 CPU (Intel, AMD) with virtualization capabilities

• 16GB RAM

• 5GB hard drive

Server only

• 2-core x86-64 CPU (Intel, AMD) with virtualization capabilities

• 16GB RAM

• 10GB hard drive

Runner only

• 2-core x86-64 CPU (Intel, AMD) with virtualization capabilities (not needed for native runner)

• 8GB RAM

• 2GB hard drive

Note that additional hard drive space is required for use, depending on the size of your projects.

Supported OS:

• Windows 10

• Windows 11

Software requirements:

Full solution

• Docker Desktop (4.26.0 or later) or Rancher Desktop (1.11.1 or later). Check that docker-compose version is at least 2.21.

Note that Docker Desktop may be a non-free solution depending on the size or revenues or your company, so you may prefer Rancher Desktop in that case.

• Visual Studio C++ Redistributable 2017. Double-click on the downloaded file and follow the steps to install it.

If you don't know if Visual Studio C++ Redistributable 2017 is already installed on your system, you may proceed with beLow installation without installing it and finally install it if it turns up that you are unable to run the user interface because of missing libraries.

Server only

• Docker Desktop (4.26.0 or later) or Rancher Desktop (1.11.1 or later). Check that docker-compose version is at least 2.21.

Runner only

No dependency is needed for runner only.

To build/run code on your system (full solution or native runner only), running local scripts must be allowed on the system. To know if your system is able to run such scripts, run in a Powershell terminal:

Get-ExecutionPolicy

If result is Restricted, then you must change the execution policy to RemoteSigned or Unrestricted (less safe). For this, open a Powershell terminal as an administrator.

You may do that by setting execution policy to your current user:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

You may also apply it to the whole local machine:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine

After running one of these commands, Get-ExecutionPolicy should return RemoteSigned.

You may still use beLow without changing execution policy, but jobs won't be able to run natively on your local system, and so you won't be able to run a Windows build or a Windows code execution.

To be able to support Docker virtualization for non-x86 platforms, the following command should be run in a non-admin Powershell terminal, while Docker Desktop or Rancher Desktop is running:

docker run --rm --privileged multiarch/qemu-user-static --reset -p yes