Public Repository

Last pushed: a month ago
Short Description
Avast Business management console
Full Description

What is Avast Business On-premise Management Console?

It's designed to help IT professionals in small to medium sized businesses secure their network and transactions leaving plenty of time for other tasks.

With Avast Business On-premise Management Console, adding critical protection to every PC, Mac, and server has never been easier.

Besides this multi-platform docker version there is also a Windows only version of the same console. Development of this console is led by a small Czech-based team inside cyber-security company Avast Software.

Please note: This is not an antivirus installer. You are about to install a solution for management of your devices, a management console through which you will be able to download and install the antivirus.

Image description

This image is meant to be used together with the image avastsoftware/management-console-db in a docker-compose application. To run the docker-compose application, you have to prepare a docker-compose.yml file.


View the Avast End-User License Agreement for the software contained in this image.

Docker compose configuration

  1. Download docker-compose.yml with the template configuration and .env with configuration properties to the same folder. If you have git installed, you can get those files by running:
    git clone
  2. Change configuration in .env file (at least the AFB_HOSTNAME property)
  3. In the directory with docker-compose.yml and .env files run: docker-compose up
  4. When the application will be started, you can access it on https://${AFB_HOSTNAME}:${AFB_WEB_PORT}

Configuration properties

The AFB_ prefixed properties has to be defined as system properties. You can create a .env file with these properties in the same directory where you'll be starting the docker-compose application and it will be automatically used by docker-compose.

Property Default value Description
COMPOSE_PROJECT_NAME afb Determines name (prefix) of docker containers and data volumes. If you use afb as the project name, docker will create containers afb_db_1, afb_server_1 and data volume afb_data.
AFB_VERSION latest released version Version of the console.
AFB_HOSTNAME Hostname that your server will be using. It has to be an existing DNS name or IP address. It will be used by the Antivirus installations to connect to the management console. You can also access your management console UI using this hostname e.g.
AFB_DB_USER bconsole DB username that will be created and used to access database in DB container.
AFB_DB_PASSWORD password Password of your DB user
AFB_DB_NAME on-premise Database name that will be used to store data for your console.
AFB_WEB_PORT 443 Port for UI
AFB_DEVICE_PORT 8080 Server port that AV will be used for communication
AFB_AGENT_PORT 8090 Server for communication with installed agent
AFB_LOG_DIR ~/avast/business/on-premise/logs Directory on your machine where the log file will be written
AFB_SEC_DIR ~/avast/business/on-premise/security Directory on your machine for storing certificates
AFB_KEYSTORE_PASSWORD password Password for the keystore.
AFB_KEYSTORE_TYPE JKS Type of keystore. Either JKS or PKCS #12.
AFB_KEYSTORE_PATH server.jks File name relative to AFB_SEC_DIR. If the file doesn't not exist, self-signed certificate will be generated to this file.

Security configuration

There are following options for securing access to your console:

  1. HTTPS with self-signed certificate (CommonName=<AFB_HOSTNAME>) is used by default (not recommended for production usage, just for demo purpose).
  2. HTTPS with own certificate (X.509 in JKS / PKCS #12). You certificate has to be usable for your AFB_HOSTNAME (or its domain)
  • PKCS #12

  • JKS

Upgrading business console server version

To upgrade business console server to newer version (newer docker image of the application), update property AFB_VERSION in .env file in your docker compose directory to the new version and run:

# restart everything with new configuration
docker-compose up

# or you can just redeploy the server and keep the DB running
docker-compose up --no-deps -d server
Docker Pull Command