docker-fai | Code for Docker image of FAI | Continuous Deployment library

Lest straighten some terminology first:

image - is an image of runnable thing, like MySql or Python. It is readonly. You can't connect to image but you can start container out of image. Container is what do the work. Container is based on image plus has it's writable layers. So all changes are saved in those writable layers even if you stop and start it again.

so db uses an image means that docker compose doesn't have to build new image for your db container. But needs to just start container with parameters you've defined. meanwhile docker composer have to build web image using your Dockerfile.

When you do docker run mysql .... you are just spinning up new container from MySql image without using docker compose, thus it is asking all the parameters you've entered in your docker compose file for db container. Don't do this, since you are using docker-compose.

Based on what log says can't connect to local mysql through socket your python script tries to connect to mysql on local host. However your docker file defines MySql as db.

So db should be the host you web tries to find mysql on. Another thing is that your web doesn't use same networks: as other pods.

p.s. you may want to check what continuers you already running before proceeding. stop all docker compose and check rest. like this:

• docker-compose down - stop and drop containers defined in composer file.
• docker ps - to see what containers are running. should be none.
• docker ps -a - to see all containers including stopped ones.
• docker stop {container id} to stop something.
• docker rm {container id} to remove container.

It seems you are deploying your Prometheus setup via a helm chart. This causes an issue as the same delimiters ({{ and }}) are used both by helm templating and the alerting templating in Prometheus.

The {{ $labels.myData }} has to reach prometheus config intact, so helm must not process it.

The simplest way would be to use: