Skip to content
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

i run dockerfile but nginx not working #149

Open
menphurk236 opened this issue May 12, 2024 · 4 comments
Open

i run dockerfile but nginx not working #149

menphurk236 opened this issue May 12, 2024 · 4 comments
Assignees

Comments

@menphurk236
Copy link

image

from image

i run docker compose up
image

but nginx for ckan not working

how to fix env (use default config ckan)

Thank you

@NCSWilson
Copy link

try separately start the nginx?
docker compose -f docker-compose.yml start nginx

@kowh-ai
Copy link
Contributor

kowh-ai commented May 14, 2024

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"

@kowh-ai kowh-ai self-assigned this May 14, 2024
@dtufood-kihen
Copy link

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: moby/moby#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
  [...]

@dtufood-kihen
Copy link

I have filed a bug report upstream: ckan/ckan-docker-base#65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants