You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 31, 2021. It is now read-only.
Now, I go to Graylog where I send my log messages and see docker's IP as the source: 172.17.0.1. Since all the instances that got docker running seem to have the same IP, I cannot really tell which instance is producing which messages! How can I get the eth0 IP? Or identify the host in some other way?
The text was updated successfully, but these errors were encountered:
Docker networking, hoorah! I'm afraid I'm not a docker user so can't help you. But, I would suggest doing some reading on how networking works in docker. It's not as straightforward as VMs.
@Moocar
The thing is, I'm not even using docker! Like I said, the app is just copied to the home dir. It's true that the instance has docker installed, but my app is not using it, so I have no idea why it's choosing docker's IP...
Would be nice to change it to prefer eth0. However I already got around that by setting my own environment variable.
It's a bit strange that the correct $HOSTNAME variable gets shadowed by that code, which overwrites it with an incorrect value. Why not just make a separate ${LOGBACK_HOSTNAME} and keep the original $HOSTNAME.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have the following interfaces on a remote AWS machine:
My app however, is not using docker and is deployed by simply copying it to home directory and running from there. I set the host in logger.xml:
Now, I go to Graylog where I send my log messages and see docker's IP as the source: 172.17.0.1. Since all the instances that got docker running seem to have the same IP, I cannot really tell which instance is producing which messages! How can I get the
eth0
IP? Or identify the host in some other way?The text was updated successfully, but these errors were encountered: