Deployment Manual / Version 2110
Table Of ContentsTo run the tools, you can either:
Start the
management-toolscontainer in interactive mode and run the tools from within. This approach has the advantage, that it provides a familiar user experience as if the tool is installed locally.Start a tool from the
management-toolscontainer directly, using the tool as the command argument and remove the container when the tool finishes. This approach has the advantage, that it can be used in the context of a script as it requires no interaction.
Regardless of the approach, you need to keep in mind the following common issues with containers:
In case you need to read from or write to files on your host, you need to mount volumes or create a bind mount.
In case the containers are placed within a user-defined network, you need to add the container to that network to access the servers you want to connect. This network configuration depends on the network plugins being used. For the localhost
docker-composedevelopment setup, this network is namedbackendand prefixed with either the value of theCOMPOSE_PROJECTenvironment variable or the name of the directory, where the compose files lies. In the development setup this will becomposebut you can find out what networks are available, by running:docker network list NETWORK ID NAME DRIVER SCOPE 181f1af50e6e bridge bridge local 2788cdf4bd7a compose_backend bridge local
3227b513840e compose_web bridge local 
494f6bdaafa8 host host local
3d8b08335372 none null local The network, where all services are put in
The network, where all services with Traefik ingress are put in
Mounting a file system path. You can mount a file system path to a docker container by using the --volume <local-path>:<container-path>
command-line option.
Adding networks. You can attach the docker container to a network using the --network <network name> command-line option.
