Set Up Docker Container Configurations for an Application Release

an application release must contain at least one component ( containers / containers advanced ) or a compose configuration file ( compose ) although it is possible to submit a docker application release without at least one component ( containers / containers advanced ) or a compose configuration file ( compose ), the docker application release cannot be later deployed to a belden horizon data operations instance the component or the compose configuration file sets up a configuration to extract at least one docker image from a docker repository to execute the docker image's respective docker container this allows the docker application release to package multiple docker images (and the respective docker containers) and deliver them to belden horizon data operations instances concurrently it is these docker images from the component/compose configuration file that will be later deployed as docker images to belden horizon data operations instances during docid\ la0klctigwifvf43fdv1u option 1 containers set up a component see the following on how to add/manage components for the containers tab \[1] show filter / hide filter search by name , image \[2] add component you can add multiple components you can't add variables for a submitted application release \[3] action menu edit you can't edit components for a submitted application release remove you can't delete components for a submitted application release more on add component when adding a new component, a docker image must be extracted from a docker registry the other available customizations enable additional configurations when executing the docker container from the extracted docker image furthermore, when customizing the docker image configurations, it is also possible to use the variables created from docid 0v6alkyrqqujd3r 2wfut as values the syntax for referring to these variables is ${variable name} where variable name is the name of the variable being used step 1 set up common parameters in this section, you will set up the initial configuration needed for a docker image’s respective docker container name assign a name for docker container see https //docs docker com/engine/reference/commandline/run/#assign name and allocate pseudo tty name it for details repository the available registry provider of the docker image see https //app archbee com/docs/vakj8zk5bi9apnycgeyqr/m6yzedyrawwydnldtoqlz and https //docs docker com/registry/ for details image the docker image registry location for a docker pull command see https //docs docker com/engine/reference/commandline/pull/#pull from a different registry for details the image registry location must be both a valid registry location and accessible by belden horizon data operations instances restart the restart policy for the equivalent docker container see https //docs docker com/config/containers/start containers automatically/#use a restart policy for details network mode the network settings for the equivalent docker container see https //docs docker com/engine/reference/run/#network settings for details enable tty see tty or t of https //docs docker com/engine/reference/commandline/run/#options and https //docs docker com/engine/reference/commandline/run/#name for details open stdin see the interactive or i option of https //docs docker com/engine/reference/commandline/run/#options and https //docs docker com/engine/reference/commandline/run/#name for details privileged see https //docs docker com/engine/reference/commandline/run/#privileged for details command the command line arguments used by the docker container’s application when it executes step 2 set up environment in this section, you can set up the environment variables that the docker container will use during its operation see https //docs docker com/engine/reference/run/#env environment variables for details step 3 set up labels in this section you can set up metadata to the docker container see https //docs docker com/engine/reference/commandline/run/#set metadata on container l label label file for details step 4 set up ports in this section, you can set up the port management for the docker container see https //docs docker com/network/#published ports for details step 5 set up volumes in this section, you can set up the data persistence mechanism for the docker container see https //docs docker com/storage/volumes/ or https //docs docker com/storage/bind mounts/ for details option 2 containers advanced set up a component this option is an upgraded version of option 1 containers set up a component see the following on how to add/manage components for the containers advanced tab \[1] show filter / hide filter search by name , image \[2] add component you can add multiple components you can not add variables for a submitted application release \[3] action menu edit you can't edit components on a submitted application release remove you can't remove components on a submitted application release more on add component in option 1 containers set up a component , there are five steps where you may enter details for a pre determined set of basic docker parameters the limitation of the previous option is that it is not possible to access and configure the remaining more advanced docker parameters when adding a new component, this second option offers a json configuration form to access and configure the remaining advanced docker parameters the form will be used to request a docker image from a selected docker registry step 1 set up common parameters the first step is a simplified version of the step 1 set up common parameters section from the previous option name assign a name for docker container https //docs docker com/engine/reference/commandline/run/#assign name and allocate pseudo tty name it for details repository the available registry provider of the docker image see docid\ l8c 9kgktffaztjtb92e1 and https //docs docker com/registry/ for details step 2 insert container create configuration json file the second step allows you to create a docker container by entering file contents for a docker container configuration json file see for details furthermore, when customizing the json file, it is also possible to use the variables created from docid 0v6alkyrqqujd3r 2wfut as values the syntax for referring to these variables is ${variable name} where variable name is the name of the variable being used \[1] import component config \[2] copy config content \[3] paste config content \[4] clear config content \[5] link to api specifications for https //docs docker com/engine/api/v1 40/#tag/container/operation/containercreate \[6] enter config content option 3 compose set up a compose this option is an even more upgraded version of the previous two options in the form of an alternative compose subsection rather than creating a component one by one like the previous two options, you are able to set up multiple components all at once by entering a yaml compose file to set up a multi container application configuration see https //docs docker com/compose/compose file/ for details furthermore, when customizing the yaml file, it is also possible to use the variables created from docid 0v6alkyrqqujd3r 2wfut as values the syntax for referring to these variables is ${variable name} where variable name is the name of the variable being used \[1] import compose file \[2] copy compose file \[3] paste compose file \[4] clear compose file \[5] link to compose file format in https //docs docker com/compose/compose file/ \[6] compose file contents \[7] view supported compose objects supported compose objects when you click supported compose objects, a list of all the supported objects displays from the right when you attempt to save a yaml compose file with unsupported compose objects, an error such as the following appears it will indicate all the invalid fields