Skip to content

fix: use official zookeeper Docker image#10

Merged
drmingdrmer merged 4 commits into
masterfrom
fix-docker-image
Jan 7, 2026
Merged

fix: use official zookeeper Docker image#10
drmingdrmer merged 4 commits into
masterfrom
fix-docker-image

Conversation

@drmingdrmer

Copy link
Copy Markdown
Contributor

Summary

  • Change Docker image from daocloud.io/zookeeper:3.4.10 to zookeeper:3.9 (official Docker Hub)
  • The daocloud.io registry is inaccessible from GitHub Actions (returns HTTP 500)

Files changed

  • test/test_acid.py
  • test/test_cached_reader.py
  • test/test_k3zkutil.py
  • test/test_zklock.py

Test plan

  • CI passes on all Python versions (3.9, 3.10, 3.11, 3.12)

🤖 Generated with Claude Code

Change from daocloud.io/zookeeper:3.4.10 to zookeeper:3.9 (official Docker Hub).
The daocloud.io registry is inaccessible from GitHub Actions (returns HTTP 500).
Zookeeper 3.9 takes longer to start than 3.4.10, causing connection timeouts.
Add wait_for_zk helper function that retries connection attempts until
zookeeper is ready or timeout is reached.
ZOO_MY_ID and ZOO_SERVERS are only needed for cluster mode.
For standalone mode (single node), these env vars may cause issues
with zookeeper 3.9.
ZK 3.9 creates different system nodes under /zookeeper than older versions.
Skip this node in test_export_hierarchy to make the test version-agnostic.
@drmingdrmer
drmingdrmer merged commit b0e2f5d into master Jan 7, 2026
12 checks passed
@drmingdrmer
drmingdrmer deleted the fix-docker-image branch January 8, 2026 03:52
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

Successfully merging this pull request may close these issues.

1 participant