The sedex Client Docker Container

In this section you get an overview of the sedex Client as a Docker container and the basic concepts involved. Before you start using the sedex Client as a Docker container, it is important to understand these concepts.

Overview of the sedex Client as a Docker container

The sedex Client Docker image allows you to run the current sedex Client as a container. All functionality provided by sedex can be used comfortably with all the advantages that containers have to offer.

The diagram below shows the main components of the sedex Client Docker container:

• sedex Client Docker Container
  The sedex Client Docker container is a standard Docker container image based on AdoptOpenJDK and Alpine Linux. It contains a normal sedex Client, which is installed and configured "ready-to-use". Some additional internal utility scripts ensure that the sedex Client runs optimally in the container and is configurable from outside.

• Permanent storage
  The sedex Client Docker container must be able to store data permanently. For this purpose, two external storage folders ("sedex-interface" and "sedex-data") must be mounted (attached) to the container. For more details see page Permanent Storage.

• Published network ports
  The sedex Client offers services on network ports, which can be reached via HTTP or HTTPS. These container ports have to be published to the outside. For more details, see the page Published Network Ports.