voting-app | Sample app to showcase GraphQL integration | GraphQL library

You should use volumes.

Volumes will allow you to map the src code folder in the container to a path outside of your container and it will not be destroyed during restart since it will be store outside of your container.

You can see a working sample with explanation here: https://github.com/nirgeier/KubernetesLabs/tree/master/Labs/09-StatefulSet

emptyDir is the default volume and it's being deleted when the pod is deleted, but I'm using it here to show you a sample on how to use volumes.

SOLVED

The solution here is not to ssh into the VM, and instead to change to the VM context with:

ContainerPort in pod spec

List of ports to expose from the container. Exposing a port here gives the system additional information about the network connections a container uses, but is primarily informational. Not specifying a port here DOES NOT prevent that port from being exposed

targetPort in service spec

Number or name of the port to access on the pods targeted by the service. Number must be in the range 1 to 65535. Name must be an IANA_SVC_NAME. If this is a string, it will be looked up as a named port in the target Pod's container ports. If this is not specified, the value of the 'port' field is used (an identity map).

Hence targetPort in service needs to match the containerPort in pod spec because that's how service knows which container port is destination to forward the traffic to.

The Docker Compose command:, or everything in a docker run invocation after the image name, overrides the Dockerfile CMD.

If the image also has an ENTRYPOINT, the command you provide here is passed as arguments to the entrypoint in the same way the Dockerfile CMD does.

For a typical Compose setup you shouldn't need to specify a command:. In a Python/Flask context, the most obvious place it's useful is if you're also using a queueing system like Celery with the same shared code base: you can use command: to run a Celery worker off of the image you build, instead of a Flask application.

For your issue, you misunderstand the image azure-vote-front. You can the docker-compose.yaml file in the Github link your provide, it creates the azure-vote-front image, but it also needs the database Redis. So it's not a single container instance, it's the multiple containers.

You can need to create the image azure-vote-front and push it to the Azure Container Registry. Also does the image Redis. Then you can change the docker-compose.yaml file like this: