You are browsing documentation for a version other than the latest stable release. Switch to the latest stable release, 2.0.

Install a Mender demo server

Following this tutorial will create a demo installation of the Mender, appropriate for testing and experimenting. When you are ready to install for production, please follow the Production installation documentation.

Bring up the environment with Docker Compose

Make sure you satisfy the server requirements before proceeding.

In a working directory, download the Mender integration environment:

git clone -b master integration-master
cd integration-master

Mender currently requires two entries in your /etc/hosts file to work with the Docker networking (typically and If these entries do not exist as you run the up script (below), it will create them for you and thus might ask for your administrative password. If you want to avoid automatic creation, you can create the entries in advance; look inside the script for the details how it is created on your host.

Mender comes with a wrapper script that brings up the environment with Docker Compose. Running this script will pull down the images and start them:

./demo --client up

If this is the first time you start the Mender server, several gigabytes of Docker images may need to be downloaded. On a 100Mbit Internet connection this may take 5 minutes.

After the Docker images have been downloaded, the up script starts the Mender services, adds a demo user with the username, and assigns a random 12 character password.

Note that this password is not stored anywhere in the Mender demo environment. Make sure to remember this password for logins to this instance of the demo environment.

When you press return log messages from the docker containers will be displayed in your terminal, including output from the Mender virtual device. Eventually, most of the logs will stop except for some periodic messages from the mender-device-auth and mender-api-gateway services. Pressing ctrl-c at any point will bring down the demo environment.

For Mender on-premise installations, your email and password are currently only used to log in to the Mender server. You will not receive any email from Mender. However, this might change in future versions so we recommend to input your real email address.

Open the Mender UI

For security reasons, the Mender gateway only allows secure connections using TLS, both for communicating with devices and end users. Your web browser will communicate directly with the gateway while using the Mender UI and therefore the certificate the gateway is using needs to be trusted by your web browser.

The Mender UI can now be found on https://localhost/ - simply open it in your web browser and accept the certificate. In Chrome it should look like the following:

Accept certificate - Chrome

Log in with your email and password you created above.

Congratulations! You have the Mender server and a virtual Mender client successfully running! Please proceed to Deploying to virtual devices.