Closed AndrzejA35 closed 4 years ago
Hello again.
I have resolved this issue and would like to share the root cause so that everyone could benefit from my investigation.
The root cause of this issue was the fact that the container couldn't reach CDS API being hosted in "host". I couldn't find the proof, because the containers were constantly being killed. I have added containers logs to the Elastic and thankfully Filebeat was able to catch all the logs from the container. Those logs confirmed connectivity issues.
Below is the final configuration of the worker model.
curl ${CDS_API}/download/worker/linux/$(uname -m) -o worker --retry 10 --retry-max-time 120 && chmod +x worker && exec ./worker
ENV VARIABLES:
...
CDS_API: http://dockerhost:XXXX
...
Bear in mind that docker container should be able to access your host. This can be done in many ways, depends on your configuration. I did this previously for other containers by adding a docker network interface to a trusted zone (CentOS) and adding docker host plus port forwarding.
I believe this issue can be closed.
Hello guys,
I do have a 0.42 version of the CDS software installed in the "binary" mode on my Centos 7 machine.
My goal was to switch from hatchery-local to hatchery-swarm, however, this seems to be impossible in binary mode (i have managed to set this up in CDS docker mode). I would like to keep my configuration in binary mode rather than migrating to docker.
I did use DEMO project model.
Below is my CDS hatchery swarm configuration.
And logs from the hatchery swarm service:
Docker events:
I don't understand why containers die immediately after being created. And what should be done to have this working?