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
docker compose up starts unhealthy datapusher #8170
Comments
Iv'e not been successful in recreating this issue...I get the timezone warning message also... |
The same commands work on another computer with docker |
We've seen some stability issues based on the latest docker updates and docker-compose, especially with datapusher. In our case, it's looking a bit like a container startup ordering issue. |
Don´t know if it is relevant here but I also had problems with getting ckan and datapusher to report as "healthy" and it seems that inside the containers they don´t think they are "localhost". Changing healthcheck in docker-compose.yml made datapusher and ckan report as healthy for me: |
OK, I'll investigate on a couple of different host machines when I get back to early Berlin next week |
CKAN version: 2.10.4
Docker version 26.0.0, build 2ae903e
Describe the bug
docker compose up
starts unhealthy containers.Steps to reproduce
git clone git@github.com:ckan/ckan-docker.git
cd ckan-docker
mv .env.example .env
docker compose up
Expected behavior
I would expect all containers to start healthy with the default configuration.
Additional details
I would expect this following to start healthily also:
The text was updated successfully, but these errors were encountered: