Module:Futurama Website/Futurama Webservice/Futurama Vision Management Site


User:System administrator


- not applicable



The versions of Futurama are now also released to Docker. All versions from Futurama 21.01 are now also available in Docker with the corresponding version number as Docker tag. We created the 'actuitnl' organization in the Docker hub, where the latest versions of Futurama are available. Using these images of the Futurama version, you are now able to run your Futurama application in a Docker container. With Docker the set up of Futurama can become easier, because you are not dependent on server specific settings. All our images are build for Docker for Windows. Docker for Linux is not supported, because Futurama runs on .Net.

Starting with Docker

Before Futurama can be ran in Docker, you first have to be added to our organization in the Docker hub. Please contact us via e-mail if you want to be added. After that you will be able to pull the latest Futurama version from the Docker hub and create your application in Docker. For more information how to work with Docker, see

Benefit of using Docker

There are multiple benefits of using Docker instead of setting up the installation in IIS. For example the updating and deployment of your application will become easier and you don't have to think about specific server settings. These examples will be explained below.

Eliminating manual steps

When using Docker, the manual steps that are needed will be eliminated. You don't have to download the version manually and copy the files to your application. Instead of these steps, you only have to change the tag to the new Futurama version and restart your Docker application. This makes the chance smaller of your application not working, because some files are missing.

You don't have to think about server settings

Next to this, you also don't have to think about server specific settings that are needed to run Docker, because these settings are already done within the Docker image we provide. For example you don't have to think about the .Net version, because this is already provided in the Futurama images.

Deployment of a new version to production

The deployment of a new version from an acceptation to a production environment will also become easier. The only difference between these environments will be the config file, all other files will be provided in the Docker images. Using Docker there is no description needed with a new version. Only the tags and potentially the config file has to be changed and then the Docker container can be restarted.

Futurama versions in Docker

Currently there are 3 Futurama editions available in Docker. These are the following:

  • actuitnl/futurama_site for the website edition

  • actuitnl/futurama_webservice for the webservice edition

  • actuitnl/futurama_vision_managementsite for the Vision Management Site edition

Windows versions

When pulling the Futurama image from Docker, the correct Windows version will be used automatically. The following versions are currently supported:

  • ltsc2016 (Windows Server 2016)

  • ltsc2019 (Windows Server 2019)

All Windows versions with build number 14xxx to 19xxx are supported with the versions mentioned above (also see this page with the build numbers of the different windows versions). You can check your Windows build number with the command "winver".

Docker layers

A Docker container is set up of multiple layers (images) that are combined when the container is started. Using this layer construction, you can separate different parts of the Futurama application to be able to update them separately. The docker images mentioned above only contains the Futurama code. In order to start a Docker container for your application, you can use the Docker image of the Futurama release as the base image. Then you can add a new layer (or layers) of images with your application specific files. This can for example be the following layers, where all the different elements are separated in different images:

  1. Futurama release code

  2. Application and application specific files

  3. Futurama license

  4. Web.config and server specific file


If you have any questions about this subject or if you want to provide us feedback please send us an e-mail.

Updated: 2021-12-27