4.1. Installation overview

AccessMod 5 comes packed inside an image, a "lightweight, standalone, executable software package that contains everything needed to run an application." This image is based on Docker, "an open platform for developing, shipping, and running applications," and can be deployed either through a virtual machine using VirtualBox or directly through Docker desktop. The virtual machine is an encapsulated operating system that runs in many operating systems that act as hosts. However, virtualization requires some computing resources, which generally makes AccessMod more efficient when using the image directly in Docker desktop. Nevertheless, the default recommended installation (highlighted below) is the combination of a virtual machine (files.ova) and VirtualBox as a virtual machine manager. The description of how to install AccessMod via VirtualBox is described next in section 4.2. Further descriptions to install and use AccessMod via Docker are described in the appendices.

The following table provides an overview of the platforms to use AccessMod, the computer infrastructures they work with, and the general type of user that might be interested in using them.

UserUsesAccessMod platformComputer infrastructureTutorial
StandardSporadic and/or simple modelsVirtualBox

.ova file for any infrastructure
Specific for VirtualBox installer
Installation process via VirtualBox
IntermediateFrequent and/or complex modelsDocker via the
electron launcher

.exe & .dmg files for Intel Windows & Apple PCs

(Currently) .dmg + update for M1 Apple PCs

Specific infrastructure installer for Docker

Installation of AccessMod via electron launcher

Installation of Docker desktop
AdvancedConstant and/or
very complex models
Docker via the
command line
Any infrastructure
Direct pull from the repository
Installation of AccessMod via
Docker compose (command line)