Edge Builder is able to deploy applications of two types. These are often refered to as
un-containerized. More specifically, we support the following application formats:
- All application formats allow configuration to be injected into one or more locations (volumes or paths).
docker-compose applications many deploy one or more containers. There are no restrictions on how the compose file is defined, however, the following constraints must be considered:
- All images used must be publicly accessable, or already avaliable on the
- The content of the compose file must be static (e.g. no enviroment variables)
- It is possible to use private docker images by creating a script to run the
docker logincommand on all
systemd applications simply define an existing systemd process to manage. On top of this they provide a list of paths to directories that configuration may be inserted into. The following should be considered when defining a systemd app:
- The systemd sevice must be avalaible on the
Node. The simplest way to achieve this is via a script, Edge Builder could be used to execute this on all
For further information and a practical example see the Un-containerized Apps tutorial.
Edge Builder provides a means of injecting configuration files into docker volumes (docker-compose) or specific paths on the
Node (systemd). Application configuration files are added individually to Edge Builder, the following types are supported:
- Tarball (supports all compression formats
Text based files are injected as specified. Tar files are extracted into the requested volume or directory.