Hi Elastic Team,
I was sent to you by the support training@elastic team. I just got my Strigo environment reset for the 3rd time but the problem still persists. My mysql docker container (
ubuntu_mysql) is shown as unhealthy after startup and stays in that state. I'm not sure if this problem has anything to do with any other Elastic Observability Engineer Lab issues but it sure confusing.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 36dbb63b31b7 training/client-loadgen:8.2.3 "dumb-init -- node_m…" 2 months ago Up About a minute loadgen f6940887104e ubuntu_petclinic-client "/root/startup.sh" 2 months ago Up About a minute (healthy) 0.0.0.0:4000->4000/tcp, 22/tcp, 0.0.0.0:8080->8080/tcp petclinic-client f8bd81246cab ubuntu_petclinic-server "/root/startup.sh" 2 months ago Up About a minute (healthy) 22/tcp, 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp petclinic-server 0fc810e5a0a6 docker.elastic.co/beats/elastic-agent:8.2.3 "/usr/bin/tini -- /u…" 2 months ago Up 2 minutes 0.0.0.0:8200->8200/tcp, :::8200->8200/tcp, 0.0.0.0:8220->8220/tcp, :::8220->8220/tcp fleet-server afa45bb3a944 ubuntu_mysql "/root/startup.sh" 2 months ago Up About a minute (unhealthy) 22/tcp, 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp mysql da02737dd4e3 ubuntu_address-finder "/usr/local/bin/guni…" 2 months ago Up About a minute 0.0.0.0:5000->5000/tcp address-finder 76a4ecfc5a8d docker.elastic.co/kibana/kibana:8.2.3 "/bin/tini -- /usr/l…" 2 months ago Up 2 minutes (healthy) 0.0.0.0:5601->5601/tcp, :::5601->5601/tcp kibana 448988aff7b2 docker.elastic.co/elasticsearch/elasticsearch:8.2.3 "/bin/tini -- /usr/l…" 2 months ago Up 2 minutes (healthy) 0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 9300/tcp elasticsearch
Is this a problem and how can I fix this issue? What is causing the unhealthy state?
Thank for your help!