Not reading es_host in elastalert.yaml

[MinnMoto]

I am working to get elastalert-docker running on a RHEL VM. I have a bit of experience with Docker, but I can not seem to figure out why this container is still looking for my server name locally, rather than reading the es_host from the elastalert.yaml.
el01_error.txt

I've attached my docker-compose.yaml to this message. Also, the first few seconds of Elastalert's startup. You'll see my host server is still being referenced. I have checked my pathing on host to ensure the correct file is being referenced.

This is a piece of my elastalert.yaml

# The Elasticsearch hostname for metadata writeback
# Note that every rule can have its own Elasticsearch host
#es_host: msplwb400
es_host: es01

# The Elasticsearch port
#es_port: 9211
es_port: 9200

TYIA,
Dan

el01_error.txt
docker-compose.yaml.txt

[jertel]

I suggest running some debug commands to see what's going on inside the container. If the container is in a crash loop you can override the entrypoint and have it sleep for 5 minutes. Ex: /bin/sh -c "sleep 300" which will give you enough time to exec into the container and view the environment variables and the /opt/config/elastalert_config.yaml to track down where that host name is leaking in.