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

Why Do We Change The Hostname Inside The Chroot? #498

Closed
afroDC opened this Issue Nov 21, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@afroDC
Contributor

afroDC commented Nov 21, 2018

There seems to be no reason why the host containers hostname is changed and also that we had the external ip address + hostname into /etc/hosts.

@afroDC afroDC added the question label Nov 21, 2018

@afroDC afroDC added this to the 3.1.5 milestone Nov 21, 2018

@mbaser

This comment has been minimized.

Collaborator

mbaser commented Dec 4, 2018

If you are inside container, you don't have access to /etc/hosts file outside of the container. And if you don't have DNS entry for hour hostname, your hostname resolution will fail inside of the container. Having ip-hostname pair in /etc/hosts file outside of the container, won't make hostname resolution inside the container.

@mbaser

This comment has been minimized.

Collaborator

mbaser commented Dec 5, 2018

Some network services uses hostname to identify itself. So if you don't set hostname inside container, some services may misbehave, and hostname outside of the container do not have any effect inside.

@mbaser

This comment has been minimized.

Collaborator

mbaser commented Dec 5, 2018

Even I unset hostname or set to localhost gluu ui seems work.

@mbaser mbaser closed this in 1f902c0 Dec 5, 2018

mbaser added a commit that referenced this issue Dec 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment