# Elastic Observability Engineer course - mysql docker container unhealthy

**URL:** <https://discuss.elastic.co/t/elastic-observability-engineer-course-mysql-docker-container-unhealthy/322075>\
**Category:** Elastic Training\
**Tags:** docker\
**Created:** [December 28, 2022, 8:00am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-mysql-docker-container-unhealthy/322075 "2022-12-28T08:00:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sl3vin](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@sl3vin](https://discuss.elastic.co/u/sl3vin)\
**Post date:** [December 28, 2022, 8:00am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-mysql-docker-container-unhealthy/322075/1 "2022-12-28T08:00:58Z")

</div>

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.

```auto
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!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 27, 2023, 8:01am UTC](https://discuss.elastic.co/t/elastic-observability-engineer-course-mysql-docker-container-unhealthy/322075/2 "2023-01-27T08:01:03Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.