Deploying with Docker#
To run Covalent as a Docker container using public images, do the following.
Prerequisites#
Install and run Docker on your remote host.
Procedure#
docker pull public.ecr.aws/covalent/covalent:latest
Note
To get the current stable image of Covalent, use stable
instead of latest
.
docker container run -d --name covalent -p 48008:48008 public.ecr.aws/covalent/covalent:latest
This starts the container in detached mode and forwards port 48008
to the host.
The following table lists the environment variables available to customize Covalent’s execution environment at startup:
Environment Variable |
Description |
---|---|
COVALENT_ROOT |
Root directory for the |
COVALENT_CONFIG_DIR |
Directory that |
COVALENT_PLUGINS_DIR |
Path where |
COVALENT_DATABASE |
Path to |
COVALENT_LOGDIR |
Path to |
COVALENT_CACHE_DIR |
Directory used by |
COVALENT_DATA_DIR |
Path to |
COVALENT_RESULTS_DIR |
Directory in which to store intermediate result objects |
COVALENT_SVC_PORT |
TCP port on which |
COVALENT_SERVER_IFACE_ANY |
Boolean flag that causes |
COVALENT_NUM_WORKERS |
Number of Dask workers in Covalent’s default cluster |
COVALENT_MEM_PER_WORKER |
Memory limit for each Dask worker |
COVALENT_THREADS_PER_WORKER |
Number of threads with which to start each worker |
docker container run --name covalent -p 8000:8000 -e COVALENT_NUM_WORKERS=2 -e COVALENT_SVC_PORT=8000 public.ecr.aws/covalent/covalent:latest