-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker-compose with link #170
Comments
Hi @artemicruz
And
|
It is not a problem, they are suggestions to improve the code.
The other containers do not have container_name:
icinga2 and mysql undeclared container_name
graphite declared container_name and
this warning will not be necessary if you use network
# Important:
# keep the hostname graphite the same as
# the name of the graphite docker-containe
For example
networks:
icingaweb2:
https://docs.docker.com/v17.09/compose/networking/#specify-custom-networks
El dom., 9 dic. 2018 a las 17:38, Jordan Jethwa (<[email protected]>)
escribió:
… Hi @artemicruz <https://github.com/artemicruz>
Can you clarify the issue you are having? Looking at the docker compose
file:
ICINGA2_FEATURE_GRAPHITE_HOST=graphite
And
container_name: graphite
hostname: graphite
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#170 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AaVaejCpZKpZWM0eDMWnAiEhEu92xHh9ks5u3Up-gaJpZM4ZKFPl>
.
|
OK, I partly get a clue, what you're talking about. But thinking further, I can't find an overall point. I don't want to sound rude, but there is a fork button, and a Pull request button. And I would like to encourage you to make use of these. In terms of communication and the only truth of this project can be found in the its code, it might be the best solution in this situation to make a PR. |
https://docs.docker.com/get-started/part3/#docker-composeyml
Communication across links
Links allow containers to discover each other and securely transfer information about one container to another container. When you set up a link, you create a conduit between a source container and a recipient container. The recipient can then access select data about the source. To create a link, you use the --link flag.
Possible solution container graphite
container_name: graphite
My thanks and congratulations to you
The text was updated successfully, but these errors were encountered: