Günter Grodotzki
Günter Grodotzki
This might be similar issue to: https://github.com/outline/outline/issues/7065
Setting `com.datadoghq.ad.*` as label and `ECS_FARGATE=true` on the _main_ container (not the datadog-agent sidecar) worked for us for our use cases. Maybe this is something specific to DBM?
Thanks @LyroStedman - should this not be configurable?
I had a slightly different error (https://issues.jenkins.io/browse/JENKINS-72415): > java.lang.IllegalArgumentException: Invalid Proxy at java.base/java.net.Socket.(Unknown Source) at org.apache.hc.client5.http.ssl.SSLConnectionSocketFactory.createSocket(SSLConnectionSocketFactory.java:208) at but fortunately latest version (`apache-httpcomponents-client-5-api:5.2.3-1.0`) resolved the issue
> Is this feature more about processing consistency at the same performance level, or no you have workloads which are CPU bound and could benefit for higher performing processors? Both....
Having distributed CI runners for sure is even important for hobby projects given the current industry standard. Not having HA or SSO are expected.
Is this maybe fixable by connecting to the dockerd via IP instead of a socket file?
> Since docker daemon has not built-in authentication by doing that you are essentially giving root access to any process that can connect to localhost IP on that host. thats...
I too would appreciate a fork if this project has been abandoned. Appreciate though the work on this @Junkern 🙇🏽