Loading the documentation…
This page covers the install in full, for IT teams and anyone who wants to know what each step does. To just install, follow the short Install DataMind OS instead.
With this server's DataMind License Key, one command checks the server, installs Docker when it is missing and starts the DataMind Installer. You then run the first installation from the Installer's screens. If DataMind issued you an Azure client secret instead, take the Azure path.
Check System requirements first: this guide assumes a Linux host, and the page lists the operating system, hardware, network access and ports your server needs.
sudo, or the root account. The install changes system
settings, so it runs as root.client_id and client_secret pair DataMind
issued you. Each server has its own License Key, which starts with dm-lic-. DataMind sends it to
you, or an Administrator of your company adds an instance under Instances in the DataMind
Platform console, where the key is shown once.platform. datamind. ai, and to Docker's download hosts while Docker is not
installed yet. Network lists them.You do not have to install Docker first. With a License Key, the install uses the Docker Engine it finds on the server, or installs Docker Engine and its Compose plugin when they are missing. Only the Azure path and the by-hand steps need Docker installed beforehand.
Skip this section on the License Key path, unless you prefer to install Docker yourself. The Azure path and the by-hand steps need Docker Engine with the Compose v2 plugin on the host: install it by following the official instructions for your Linux distribution: Docker Engine installation.
To run the docker commands of those steps without sudo, add your user to the docker group:
sudo usermod -aG docker $USER newgrp docker
Membership of the docker group gives the same control of the server as root. The License Key path
does not need it and adds nobody to the group.
Install it with this server's License Key, or take the Azure path if DataMind issued you a
client_id and client_secret instead.
Download the install script and run it:
curl -fsSL https://platform.datamind.ai/install.sh -o install.sh && sh install.sh
Paste this server's License Key when the script asks DataMind License Key:. The key is not
shown as you type.
When sudo asks for your password, enter it. The script prints
Downloading DataMind setup from platform., checks the download and runs
DataMind setup as root. Run as root, nothing is asked.
Read the checks. DataMind setup first checks the server and changes nothing while it does. Each
line reads [ PASS ], [ INFO ], [ WARN ] or [ FAIL ], and the Summary repeats the
warnings, because they scroll past. It then asks
Preflight passed., or, when the checks warned about
anything,
Preflight passed with <n> warning(s), listed above..
Choose Install to go on, or Stop to leave the server as it is.
Confirm Docker's address ranges. Under Docker needs address ranges of its own it shows the
ranges it picked and asks Use these ranges?. Choose Accept, or Change to enter the
ranges your network team gave you. Docker's address ranges explains the
choice. Ranges already set in Docker's configuration are kept, and this question is skipped. A
Docker that already runs containers is asked about first; see
A Docker that is already in use.
DataMind setup then installs Docker if it is missing, creates the shared Docker network, signs in to
platform. with the key, pulls the DataMind Installer, writes its Compose file and an
. holding the key in the install directory, by default one under /, and starts it. It waits
until the Installer reports healthy. Every image, file and update then comes from
platform.. What the install changes on the server
lists every change.
that License Key is incomplete - copy it again.install. sh: platform. datamind. ai refused the License Key - check it under Instances on platform. datamind. ai.That is an API key - the Installer exchanges it at its first update., and the Installer swaps it
for this server's own License Key at its first update.Preflight found blocking problems. Nothing was changed., followed by
Fix the problems above, then run: and the command to run once you have fixed it.Stopped during: <step>, the changes made so
far and the command that carries on. Running it again is safe.
Troubleshooting lists the messages.Check it worked. DataMind setup ends with The DataMind Installer is running. and the address to
open: the server's public address, such as http:/, marked
public address, as the DataMind Platform sees it, followed by the addresses the server knows itself
by. The public address is the one the server's requests reach DataMind Platform from. When the server
goes out through a proxy or reaches the platform over a private network, setup cannot tell it, and the
line reads http:/ instead. The page is plain HTTP. Across a network you do not control, open it through an SSH tunnel instead:
ssh -L 8000:127.0.0.1:8000 <you>@<this server>
Then browse to http:/. If the Installer answers on the server but the page does not
load from your machine, inbound TCP 8000 is blocked in front of the server. Allow it from your own
address only: the Installer configures the whole platform and should never face the open internet.
For an unattended run, run the command as root with PLATFORM_API_KEY set to the License Key.
Without a terminal and without the variable, the script stops with
install.. Without a terminal
DataMind setup asks nothing: it uses the address ranges it detected, and it leaves a Docker that
already runs containers as it is. To install somewhere other than the default, set INSTALL_DIR.
If DataMind issued you a client_id and client_secret instead of an API key, install from Azure:
Create the install directory and download the Docker Compose file from the address in your licence details:
sudo mkdir -p <install directory> && cd <install directory> sudo curl -fsSL <compose file address> -o docker-compose.yml
Log in to the registry, create the shared network, pull the images and start the stack:
docker login -u <client_id> <registry> docker network create <network> docker compose pull docker compose up -d
The registry host is in your licence details, and the network name is the one the Compose file expects.
When docker login prompts for the password, enter your client_secret.
Check it worked. The DataMind Installer answers on http:/ once the containers
start.
The published script is the recommended route. If you cannot run it, these are its steps:
Sign in to the DataMind Platform gateway with your key:
docker login -u apikey platform.datamind.ai
Paste this server's License Key as the password when prompted.
Render the Compose file with the Installer image's print-compose helper. Every image in it
points at the gateway, so the host needs no Azure access:
sudo mkdir -p <install directory> && cd <install directory> docker run --rm -e PLATFORM_REGISTRY_HOST=platform.datamind.ai \ <installer image> print-compose > docker-compose.yml
The host value must be a bare host[:port]. Anything else stops with
print-compose: PLATFORM_REGISTRY_HOST must be a bare host[:port], got '<value>'.
Copy . to ., and set PLATFORM_API_KEY to the License Key and
PLATFORM_REGISTRY_HOST to platform.. The key seeds the Installer on its first
start only; see Configuration for how it is managed
afterwards.
Create the shared network and start the stack:
docker network create <network> docker compose pull docker compose up -d
The network name is the one the Compose file expects.
Check it worked. The DataMind Installer answers on http:/.
Open http:/. On a brand-new install the first visit shows the account form:
create the first administrator (Create admin account). Use a password that meets the
Installer's rule: at least 8 characters with an uppercase letter, a lowercase letter, a number
and a special character (Users keeps the full rule). The
form appears only while no account exists; once an administrator exists, this screen is a
sign-in form instead, and a registration attempt answers
An admin account already exists. A DataMind Platform Administrator of
your company can click Continue with DataMind Platform above the form instead: it creates
the first administrator from their DataMind Platform account.
(Sign in, sessions and account covers signing in and sessions.)
Sign in. On a fresh host the Status screen shows the setup view; click Start. This does not
start anything yet; it opens the setup chooser Set up DataMind OS, which asks
Is this a fresh install, or are you migrating an existing Jenkins-managed setup?. Status offers
Start until DataMind OS has containers on this host, or this Installer has installed or
started it before. Images already on the host do not count, so a host where the install script
has just set up the Installer shows Start.
Choose First-time install (A brand-new DataMind OS on this machine.).
Configure Platform opens and asks How will people reach DataMind OS?. When the install
script saved this server's License Key, the step shows only the two cards. When no key is
stored, it adds This server's DataMind License Key is needed too. and shows two fields above the
cards: paste this server's key in DataMind License Key
(Paste this server's License Key (dm-lic-…)), or, if you installed with Azure credentials, your
secret in Azure client secret (Only without a License Key).
Click a card. There is no Next button: the card opens its next page.
Encrypted. Needs a domain name and its certificate.), when
people open DataMind OS at a domain name and you have its certificate and private key.Not encrypted. People open DataMind OS at the server's address, usually its IP.)
otherwise. If you chose HTTPS and have no domain or certificate yet, Back returns to
this choice.The cards turn on once the Installer has checked whether a key is stored. Without a stored key,
a key or a secret, a card stays on this page and answers
This server's DataMind License Key is required.
Give the address:
http:/ / 10. 0. 0. 5. Click Finish.Finish stores the key or the secret you entered, after checking a key with the platform, downloads the install files if they are not on the host yet, and saves the address, with the certificate for HTTPS. The modal then shows the saved address, and the Advanced configuration screen opens by itself. Change how DataMind OS is reached, under the address, starts the choice again. If you come back before starting the install, the button reads Review configuration and opens the settings again.
On Advanced configuration, every value falls back to its default when left empty, so change
only what you need now. PLATFORM_URL, and for HTTPS SSL_CERT_PATH and SSL_KEY_PATH, already
hold what Configure Platform saved.
Click Start Installation. The confirm dialog reads
Installation deploys DataMind OS with the current configuration; you can still change values and restart afterward.
Confirm with Start Installation, or go back with Go back. Any changes you made are saved
as the installation starts.
Watch the installation:
Downloading catalog…, then
Preparing deployment job….Finalizing pull — waiting on <services>.Installation failed; open job logs from the toast. The
Service status screen holds the full Job Logs panel.When the last service finishes, the hub switches to the running view: the deployment is up.
DataMind OS now runs at the Platform URL you entered; the address pill at the top of the Installer opens it too. Sign in to DataMind OS for the first time with the administrator created during setup, or create the first administrator if the server has none: First sign-in to DataMind OS.
DataMind setup, the program the install command downloads and runs, checks the server before it
changes anything. The checks only read: the processor and the tools it needs, CPU, memory and free
disk, Docker's configuration, the clock, the networks the server knows about and the address ranges
Docker would get, a Docker that already runs containers, an existing DataMind Installer, the proxy,
the connection to platform. and the License Key, the ports DataMind needs, and on-access
virus scanning. A [ FAIL ] line stops the install, because DataMind cannot run there or the install
would harm the server. Every other finding is a [ WARN ] with its reason.
To show the result to your IT team first, run the install command and choose Stop at
Preflight passed.. The run ends with
Stopped before making changes., and the full report is in
/.
After its first run, DataMind setup stays on the server as datamind-setup, and this runs the same
checks, asks nothing and changes nothing:
sudo datamind-setup preflight
It lists every network it found and where it learned it, every port DataMind needs and what holds it
today, and the address ranges Docker would be given and why. Add --verbose to see all of it on
screen; the log always has it. It checks the License Key too when PLATFORM_API_KEY is set and kept
through sudo: sudo --preserve-env=PLATFORM_API_KEY datamind-setup preflight. It ends with
Preflight only: nothing was changed. and exit code 0 when the install would go ahead, or with
Preflight found blocking problems. and exit code 1 when something blocks it.
Docker gives its networks private address ranges of their own. Where one of them overlaps a network your server reaches through a router or a VPN, such as another office, a data source or the subnets your users sit on, the server can no longer reach machines on that network, and SSH sessions from them drop. Docker checks only the networks attached to the server itself before it picks a range.
DataMind setup looks wider. It reads the networks this server knows about: its interfaces and routes, VPN configuration, firewall rules, DNS servers, network mounts, SSH sessions and known SSH hosts. It picks ranges clear of all of them and shows them before Docker is installed or changed:
docker0 bridge: the bridge's own address with its mask.container networks: the base range Docker splits into / 24 networks for its containers.The server cannot see subnets it has no route to, so it asks Use these ranges?. Choose Accept,
or Change if your network team knows the ranges are used elsewhere. Change asks for the two
ranges they confirmed free: docker0 bridge address, for example 10., and
Base range for container networks, for example 10.. A range that overlaps a network
found on the server is used with a warning, because you chose it.
Ranges already set in / are kept as they are, and nothing is asked about
them. To give Docker your own ranges on a run without a terminal, add them to the file before you run
the install command, for example:
{ "bip": "10.99.0.1/24", "default-address-pools": [{ "base": "10.99.64.0/18", "size": 24 }] }After the first run you can also give them on the command line. To replace ranges the file already
sets, add --yes:
sudo datamind-setup --docker-bip 10.99.0.1/24 --docker-pool-base 10.99.64.0/18
DataMind setup never rewrites / or restarts Docker without your yes when
Docker already runs containers, or when DataMind is already installed on the server. It shows
Docker is already in use on this server, what it would change and what leaving Docker alone means,
and asks Change Docker now?:
Without a terminal, Docker is left as it is, with the same exception. To move it onto the new ranges
later, run sudo datamind-setup --yes in a maintenance window. A Docker with nothing on it yet is
restarted without asking, because there is nothing to interrupt.
If Docker runs rootless on the server, DataMind setup asks Use the system Docker for DataMind?
before it installs or starts the system Docker beside it, because that changes how the server is
secured. DataMind runs on the system Docker; Stop ends the install. A server runs one DataMind
Installer: if one is already installed in another directory, the run stops before any change and
prints the command that brings it up to date where it is.
After you choose Install, DataMind setup makes these changes, in this order:
| Change | Where |
|---|---|
| Saves the platform, the release channel and the install directory, so a later run needs no options | /, readable by root only |
| Puts itself on the server, so you can run it again by name | / |
| Adds Docker's address ranges, and your proxy when Docker needs it. Every other setting in the file is kept, and an existing file is saved first | /; the previous version is saved as / |
| Installs Docker Engine and the Compose plugin when they are missing, starts Docker, and restarts it once when it must take up new ranges | Docker's own packages |
| Creates the shared Docker network the DataMind Installer and DataMind OS use | Docker |
| Signs the root account in to the registry with the License Key | platform. |
Downloads the DataMind Installer, then writes its Compose file and an . holding the License Key; every other line of an existing . is kept | docker-compose. and . in the install directory, by default one under / |
| Pulls the Installer's images, starts it and waits until it reports healthy | Docker |
| Logs the whole run. The log records every network the server knows about, so only root can read it | / |
On RHEL 10 and its rebuilds, when the kernel lacks a module Docker's networking needs, it also installs
the kernel-modules-extra package before Docker starts. It adds nobody to the docker group.
When a step fails, DataMind setup prints Stopped during: <step>, then the changes it made so far,
under Changes made to this host before stopping, so you know what is there:, and the command to
run once the problem is fixed.
Running it again is safe: it keeps what is already done and carries on. After the first run, from any directory:
sudo datamind-setup
It uses the platform and install directory saved at the first run, asks for this server's License Key
again, runs every check, then asks before it changes anything. Running the install command again does
the same with a fresh download, and keeps the saved install directory unless you set INSTALL_DIR.
It is not how you update. The DataMind Installer updates itself, from its own screen; see Update the DataMind Installer.
Behind a proxy, keep your proxy settings through sudo, or the checks run without them. DataMind
setup warns when sudo removed them and prints the command, for example
sudo --preserve-env=https_proxy,http_proxy,no_proxy datamind-setup. The install command keeps them
by itself; see Through a proxy.
A Linux server on x86_64, an account that can use sudo, and either this server's DataMind License
Key or the client_id and client_secret DataMind issued you. See
System requirements for the OS, hardware, network and
ports.
It runs DataMind setup as root with sudo, because the setup installs Docker and writes system
settings such as /. sudo asks for your password; run as root, nothing is
asked. Nothing changes before you choose Install.
Yes. Run the install command and choose Stop at the question that follows the checks: nothing
changes, and the report is in /. After the first run,
sudo datamind-setup preflight runs the same checks without asking anything. See
Have the checks reviewed before anything changes.
Yes. It keeps what is already done and carries on, and it never changes or restarts a Docker that runs
containers without your yes. After the first run, sudo datamind-setup does the same with the saved
settings. See Run it again.
Accept the ranges DataMind setup shows, unless your network team knows they are used somewhere this server cannot see, such as another office or the subnets your users sit on. Then choose Change and enter two private ranges they confirmed free. See Docker's address ranges.
Use the License Key if you have one: with it, every image, install file and update comes from
platform., and the host needs no Azure access. Use the Azure client secret only if
DataMind issued you one instead of a key.
No. Each server needs its own. The first DataMind OS that checks in with a License Key keeps it, and another server that presents the same key is refused. Add an instance for each server.
Choose HTTPS on Configure Platform, enter the domain, and upload the certificate and its private key or give their paths on the server. The Installer checks the domain and the certificate, and Finish saves them once no check failed. To change the certificate after the install, set the paths in Configuration and click Apply changes. TLS and certificates has the full steps and every check.
The percentage stops at 99% until every service group finishes its images, and the chip
Finalizing pull — waiting on <services> names what is still pending. Wait for it to clear; the
services then start.
Open the Platform URL. That is your DataMind OS address. Continue with First sign-in to DataMind OS.