🐳Docker Information

The emaildelivery.com platform runs as a collection of Docker containers using Docker orchestration. A comprehensive overview of Docker is outside of the scope of this document.

To view your running Docker containers and their resource utilization, run the following command:

docker stats --no-stream

You'll see the following containers running:

edcom-proxy

edcom-segments

edcom-tasks

edcom-webhooks

edcom-api

edcom-cron

edcom-database

edcom-cache

edcom-screenshot

edcom-smtprelay

By default, Docker containers write their output (STDOUT and STDERR) to the console. This behavior is similar to running a process in your command line interface, where it prints output to your terminal.

Logging

If you run a Docker container in detached mode (with the -d or --detach option), the output won't be displayed in your terminal because the container runs in the background.

Access the output of a running docker container with the docker logs command:

docker logs edcom-proxy

By default, when a docker container is started, container output is logged ephemerally in the following directory structure.

/var/lib/docker/containers/[container-id]/[container-id]-json.log

Container logs are automatically deleted by docker when the container is shut down

To bring your platform up run the following command in the edcom-install directory:

docker compose up -d

To bring your platform down run the following command in the edcom-install directory:

docker compose down 

To verify you have the emaildelivery.com docker images loaded, run the following command:

docker images

To load the emaildelivery.com docker images required to bring up your platform with docker compose, run the following command in the edcom-install directory:

./load_images.sh

As a nuclear option troubleshooting step, you can destroy all of your docker images and containers in one go to start over with the following command:

docker kill $(docker ps -q) ; docker rm $(docker ps -a -q) ; docker rmi $(docker images -q)