Links deployment about centurion HOT 3 CLOSED

We don't currently support linking because it assumes that things are running on the same host and we don't really have anything like that. Everything we have here has their DB environment injected via environment variables at deployment time. You can almost achieve the same thing by:

1. Giving your container a custom hostname that is not the docker server's hostname. (we don't support this, but it's a few minutes fix. I'm going to look at that now.) Currently this sets it to the docker server's hostname which is problematic.
2. Deploying your database container to a known port
3. Setting an environment variable in your Centurion config for the service telling it the name of the Docker host and the known port. You can use the %DOCKER_HOSTNAME% special interpolation in the environment variable. So your config for the service would be something like:

set(:container_hostname, 'my-container')
env_vars DB_SERVER: "%DOCKER_HOSTNAME%:12345"

That will interpolate the docker server's hostname into the env var, and assumes your DB is running bound to port 12345.

Of course, if you want first class linking, it would be totally reasonable to add it. But it needs to go into the API calls.

from centurion.

This branch: https://github.com/newrelic/centurion/tree/setting-hostnames allows you to set the hostname inside the container. Give it a shot and I'll merge if it solves your need. You just:

set(:container_hostname, 'my-container')

from centurion.

Great thank you @relistan. I will give it try a let you know.

You're right, in my use case I'm having all on the same server but after having read your comment, I just think that I only have to define the server IP as localhost and that's all :)

Thank you again, I'll let you know.

from centurion.