Running Docker-Contained Server Components in the Background
Once you have the component running as per the previous procedure, you now have the option of running in the background. ICE does not required that you run components in the background. Running a Docker container in the background, also known as running it in detached mode, offers the following advantages:
Freeing Up the Terminal: When you run a container in the background, your terminal remains available for other commands and tasks. This is particularly useful for long-running processes or services that don’t require constant interaction.
Continuous Operation: Background containers can continue to run independently of your terminal session. This ensures that your applications or services remain active even if you close the terminal or disconnect from the server.
Resource Management: Running containers in the background allows you to manage multiple containers more efficiently. You can start, stop, and monitor containers without interrupting other tasks.
Scalability: Detached mode is ideal for scaling applications. You can easily start multiple instances of a containerized service in the background, which is essential for load balancing and high availability.
To run the container in the background
2. On the command line In the ICE Agent host, press CTRL+C to stop the component.
3. Run the same command (as shown below), replacing the -it flag with -d as shown below:
docker run -d \
--net=host \
--mount type=bind,src=</path/on/disk>,dst=/app/conf \
instantconnect/ice-agent-3.6.5:2793 \
agent external \
-s https://<ICE URL>:443 \
--api-key "<API_KEY>" \
--group "<GROUP_CODE>" \
<COMPONENT> # specify either patch or rallypoint or reflector
4. Return to ICE Desktop and verify that the component appears in the specified Group and that the component is operating as expected.
Note: To update the page data, click the
Refresh button to the left of the page title.
