-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Don't set hostname to service name when using --x-networking #2327
Comments
for example with:
you cannot scale rqworker because the all end up with the hostname |
This is because of #2276. networking was supposed to use the hostname, but it didn't end up happening. Can you tell me more about how it breaks? Isn't the hostname only internal to the container? |
@dnephin it's an issue for me because
|
@dnephin is there a way to hack the compose file to use
|
There is not. We'll have to fix this for 1.5.1 |
Using the new networking features, when you start a container.
The name is correctly
<folder>_<service>_1
but the hostname is<service>
It's impossible the scale the containers in some case because all the containers get the same hostname.
The text was updated successfully, but these errors were encountered: