-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Agent conflicts with Docker Registry on port 5000 #4229
Comments
That is the go-expvar server port. It can be changed without conflict |
Indeed, the port (default: datadog-agent/pkg/config/config_template.yaml Lines 213 to 216 in 07f5937
The only exception is if you've set up the We are aware that there is a chance that port |
Port 5000 also conflicts with GitLab omnibus container. |
I'm running into this issue with an ECS Fargate container, does anyone know which env var is able to change the DD agent port from 5000 to something else? thanks |
@pablocompagni-contractorvp You can see it in one of the earlier posts but the setting is |
Can confirm setting |
I encountered this issue and it took a while to work out what was going on. I was following this documentation: The issues were:
Mentioning port 5000 in those docs would've saved me a lot of pain! Setting |
This was quite the unexpected thing to wake up to this morning. We did a GitLab scheduled maintenance reboot overnight, and then woke up to all our CI pipelines failing. It was a mad scramble for a few hours to figure out that our DD agent was port binding before the Docker registry :( Thanks for the information here! I was able to get this resolved with your help. I do hope that Datadog considers changing the default port to something far less common. A handy trick is to set the |
Just run into this following: https://www.datadoghq.com/blog/deploy-dotnet-core-aws-fargate/ Especially awkward since ASP.NET Core containers default to port 5000! |
Also ran into this. For those also needing port |
Also conflicts with default nginx config on AWS Elastic Beanstalks.
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/nodejs-platform-proxy.html |
Hi @baarney (and others in the thread), |
On ubuntu 20.04 got to /etc/datadog-agent/datadog.yaml file and uncomment the line containing expvar_port and change its value to a port you don't use.
Before everything stopping datadog-agent service and restarting it after the value change is needed. This has solved my issue. |
Describe what happened:
After installing the agent on our GitLab server, we encountered issues with GitLab Container Registry. The issue didn't appear immediately after the agent was installed but after the scheduled server update follower by the restart.
Suddenly, all attempts to push to the container registry started to fail with 404 error. It significantly disturbed the work of our development team, because it was working and out of the blue stopped working.
After checking GitLab omnibus logs, I found out that the Docker registry keeps restarting, reporting that 127.0.0.1:5000 is already in use. Then I found out that the agent is listening on that port.
I had to change the agent settings so it doesn't use port 5000 and I don't really know what consequences it would have on the agent itself.
Describe what you expected:
Since GitLab integration is one of the standard integrations of Datadog, I was not expecting that it will come in direct conflict of the widely used GitLab component, such as the container registry.
Steps to reproduce the issue:
Install GitLab using Omnibus and enable the container registry. Check if everything works as expected. Install the Datadog agent on the same machine, reboot the machine and observe that the GHitLab container registry keeps restarting because port 5000 is already in use.
Additional environment details (Operating System, Cloud provider, etc):
Ubuntu 18.04
The text was updated successfully, but these errors were encountered: