Skip to content
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

Default NAT network‘s performance is poor #780

Closed
xiaoping378 opened this issue Sep 9, 2016 · 6 comments
Closed

Default NAT network‘s performance is poor #780

xiaoping378 opened this issue Sep 9, 2016 · 6 comments

Comments

@xiaoping378
Copy link

xiaoping378 commented Sep 9, 2016

I'm just worried about the default bridge network performance, Should we use hosts Network Driver default ? because the project harbor called "An enterprise-class container registry server".

related docker issue is here

@xiaoping378 xiaoping378 changed the title Default NAT network‘s performance is bad Default NAT network‘s performance is poor Sep 9, 2016
@xiaoping378
Copy link
Author

when i tried to change the bridge mode to hosts, i met too many errors...

@reasonerjt
Copy link
Contributor

what is hosts network driver? I think you mean the host network mode? By default we'll use bridge as other option such as ipvlan is 1.12 only. If you switch to host network not sure how dns will work I haven't try, if you want to change you may need to figure out yourself

@xiaoping378
Copy link
Author

so the default bridge mode is OK?
i mean the performance is acceptable ?

@xiaoping378
Copy link
Author

xiaoping378 commented Sep 12, 2016

proxy, ui and job_service both need bind the port 80.
i have changed to host mode, and docker-compose up, i can access the UI and login OK.
but i don't know what the job_service is, Just change the port of job_service to 8000 , Now i can't docker push images OK ....
Hi @reasonerjt , how should i do ?

@reasonerjt
Copy link
Contributor

If you cannot figure out I suggest not use host mode for now.

@xiaoping378
Copy link
Author

OK, Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants