Open menphurk236 opened 4 months ago
try separately start the nginx? docker compose -f docker-compose.yml start nginx
Is the CKAN container healthy and remains in that state for at least 5 minutes? The nginx container will not start until CKAN is deemed "healthy"
The Nginx container fails to start because the CKAN container never reports as healthy, which is due to the health check failure of the CKAN container.
The health check (wget http://localhost
) fails because the IPv6 loopback address (::1
) appears to be non-functional within the container. However, the IPv4 loopback address (127.0.0.1
) operates correctly. This issue also affects the Datapusher container.
docker compose exec -it ckan wget -O /dev/null http://localhost:5000
Connecting to localhost:5000 ([::1]:5000)
wget: can't connect to remote host: Connection refused
docker compose exec -it ckan wget -O /dev/null http://127.0.0.1:5000
Connecting to 127.0.0.1:5000 (127.0.0.1:5000)
saving to '/dev/null'
null 100% |*************************************************************************************************************************| 11617 0:00:00 ETA
'/dev/null' saved
This issue is related to this change in Docker: https://github.com/moby/moby/pull/47062, and it seems to primarily affect those running Docker version 26.
$ docker version
Client: Docker Engine - Community
Version: 26.1.1
To work around this problem, you can disable IPv6 in the containers in the docker-compose.yml
file:
ckan:
[...]
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
[...]
datapusher:
[...]
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
[...]
I have filed a bug report upstream: https://github.com/ckan/ckan-docker-base/issues/65
from image
i run docker compose up
but nginx for ckan not working
how to fix env (use default config ckan)
Thank you