docker-elastic-agents-plugin icon indicating copy to clipboard operation
docker-elastic-agents-plugin copied to clipboard

Docker-based elastic agents for GoCD

Results 11 docker-elastic-agents-plugin issues
Sort by recently updated
recently updated
newest added

It appears that the "clusterSpecificAgentInstances" in the "DockerPlugin" class becomes stale and inconsistent over time. When a SERVER_PING request is sent from the server it provides a list of agents...

The client currently used is effectively EOL: https://github.com/spotify/docker-client It also has a lot of dependencies on other libraries which cannot be upgraded (e.g Jersey) who themselves have reported vulnerabilities (which...

help wanted

When running GoCD with the Docker Elastic Agent Plugin (v3.0.0-245), if the creation of the container fails (example log below) then the container is left in a "Created" state, and...

nothing in the Readme (nor in bootstrap-via-installer or bootstrap-with-installed-agent) helped with custom agent containers to work with the elastic agent. after spending a whole day knocking my head against this,...

I searched around the interwebs and docs but haven't found a way to define on which network the agents should be attached. I use an docker-compose to start up the...

If you for example do docker-in-docker ( docker:did ) or a usual remote docker-eninge, you would connect using a tcp socket rather then a lock unix socket. This socket is...

This might not be the right place for it (should it be part of docker-swarm elastic agents or k8s maybe?). However, it will do for now. The idea I want...

No matter what happened after that, whenever we get docker-engine communication is working but the container never starts, extract the docker container logs `docker log

Given I am in an Linux elastic GoCD agent When I run more than 3 acceptance tests in parallel with headless chrome Then the tests crash because I ran out...