Change virtualenv to venv.

.gitlab-ci.yml

@@ -4,9 +4,8 @@ stages:
   - test
 
 before_script:
-  - apt-get -qq update 
-  - apt-get install -y python3-virtualenv virtualenv
-  - /usr/bin/virtualenv python
+  - apt-get -qq update
+  - python3.8 -m venv python
   - . python/bin/activate
   - pip3 install -r requirements.txt
   - cp config/sample-production.engine.ini config/engine.ini

docs/bare-metal-installation.md

@@ -44,10 +44,10 @@ If you are developing engine you also might want the projects `steering`, `dashb
 
 ## Preparation
 
-In case of an development environment, create a virtual env for your Python dependencies:
+In case of an development environment, create a virtual environment for your Python dependencies:
 
 ```shell
-virtualenv -p python3.8 python
+python3.8 -m venv python
 ```
 
 No worries, the resulting `python` directory is excluded from the git respostory.

docs/developer-guide.md

@@ -62,7 +62,7 @@ The following steps espect you having done the bases configuration and set up a
 If you don't have already, you'll need to create an virtual environment:
 
 ```shell
-~/code/aura/engine$ virtualenv -p python3.8 python
+~/code/aura/engine$ python3.8 -m venv python
 ```
 
 Then you can start the engine. The following command includes the activation of your virtual environment, which you have created during the installation step (`source python/bin/activate`):