name-db | : rocket : A multilingual collection of names | Translation library

I was missing a dependency:

UPDATE

There are two ways you can handle error messages in MVC.

1. Use an error.html template. Spring boot will automatically use this template if it encounters any uncaught exceptions within controller method.
2. Catch the exception in your controller method and add appropriate error message to your model. You can then use the error message somewhere in your index.html or home.html

You can do something like,

I thought I had Docker setup on my machine, which runs Fedora 32. However as I came to realize from this article, setting up Docker on Fedora 32 requires some extra steps I was not previously aware of.

Specifically for this issue, the command listed in the article to add Docker to whitelist Docker on the local network's firewall with the command

A container will only be reachable from outside Docker space if it has published ports. So you need to remove the -p option from your database container.

For the two containers to be able to talk to each other they need to be on the same network. Docker's default here is for compatibility with what's now a very old networking setup, so you need to manually create a network, though it doesn't need any special setting.

Finally, you don't need --net host. That disables all of Docker's networking setup; port mappings with -p are disabled, and you can't communicate with containers that don't themselves have ports published. (I usually see it recommended as a hack to work around hard-coded localhost connection strings.)

That leaves your final setup as:

But what happens when you have multiple deployments inside a service for the same app (each having their app - database container pair)? How will the service know which app pod will communicate with what database pod? Does there now need to be a separate service for every app and database deployment?

What do you mean by "multiple deployments inside a service" ? In a Service definition you are supposed to select only one set of Pods, let's say managed by one specific Deployment. As @Matt suggested, you should always create a service with a unique name for each pod/db you want to access. If you have Pods dedicated to do specific tasks you deploy them separately (as separate Deployments). They can even consist of just one Pod if you don't need any redundancy. And basically you will always create a separate Service ( obviously with unique name as you cannot create more Services using the same name ) for exposing different microservice ( represented by unique Deployment). Note that if you don't create a Deployment but a simple Pod it won't be managed by any controller so if it crashes, nothing will take care of recreating it. So definitely you should always use Deployment even to run a single Pod representing your microservice.

Have you read this topic in official kubernetes documentation ? If you don't specify Service type, by default it creates so called ClusterIP Service which is basically what you need to expose your app components internally (make them available for other app components in your cluster).