Skip to content
Discussion options

You must be logged in to vote

I found what cause problem.

Crawler fails to connect to Chrome on Docker hosts with IPv6 enabled

Root Cause

# Broken host — resolves to IPv6
$ docker exec karakeep-web-1 getent hosts chrome
fdd0:0:0:8::2   chrome

# Working host — resolves to IPv4
$ docker exec karakeep-web-1 getent hosts chrome
172.18.0.4      chrome

Seems that karakeep resolver only handles IPv4 addresses.

Workaround

Explicitly disable IPv6 on the internal Docker network in docker-compose.yml:

networks:
  int:
    enable_ipv6: false

Then recreate network and full stack:

docker compose down && docker compose up -d

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by eiacub
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
bug Something isn't working status/untriaged This issue needs triaging to confirm it
2 participants
Converted from issue

This discussion was converted from issue #2551 on March 16, 2026 07:28.