testcontainers / testcontainers/testcontainers-python

Question: Cannot start KafkaContainer() (on windows(?))

未关闭
#1,015 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

📖 documentation
主要语言
Python
星标
2.3k
派生
386
平均合并
4 小时 40 分钟
30 天内合并 PR
1

描述

I am trying to create a KafkaContainer for my integration test, but I have issues starting it.

Using testcontainers==4.12.0, the following snippet has no issues:

from testcontainers.kafka import KafkaContainer
kafka_container = KafkaContainer()
kafka_container.start()
kafka_bootstrap_servers = cls.kafka_container.get_bootstrap_server()

However, upgrading to testcontainers==4.14.2, the same snippet gives the following issue:

Traceback (most recent call last):
  File "...\test.py", line 42, in setUpClass
    cls.kafka_container.start()
  File "...\env\Lib\site-packages\testcontainers\kafka\__init__.py", line 192, in start
    self.tc_start()
  File "...\env\Lib\site-packages\testcontainers\kafka\__init__.py", line 165, in tc_start
    port = self.get_exposed_port(self.port)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\env\Lib\site-packages\testcontainers\core\container.py", line 251, in get_exposed_port
    return self._get_exposed_port(port)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\env\Lib\site-packages\testcontainers\core\container.py", line 257, in _get_exposed_port
    return int(self.get_docker_client().port(c.id, port))
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "...\env\Lib\site-packages\testcontainers\core\docker_client.py", line 170, in port
    raise ConnectionError(f"Port mapping for container {container_id} and port {port} is not available")
ConnectionError: Port mapping for container 06001694f7ed34dac7f89c4f3a3488d23a884338ec2cc8b367120c2452d39382 and port 9093 is not available

I did a simple investigation and found out that the waiting logic has changed between these two tags. When I use tag 13.0 and 13.1, there is a "legacy deprecation warning" but KafkaContainer can still be started.

...\test.py:40: DeprecationWarning: The wait_for_logs function with string or callable predicates is deprecated and will be removed in a future version. Use structured wait strategies instead: container.waiting_for(LogMessageWaitStrategy('ready')) or container.waiting_for(LogMessageWaitStrategy(re.compile(r'pattern')))
  wait_for_logs(cls.kafka_container, "started")

Specifically, the ConnectionError I mentioned above occurred when I upgraded 13.1 to 13.2. The changes I suspect could cause this would be this line

Not sure if this is caused by wrong usage of the library or my personal setup. It is worth noting that I have to disable Ryuk when running the code snippet (using TESTCONTAINERS_RYUK_DISABLED=true) and I am running the code snippet from Windows cmd.

Let me know if there are more information I could provide to investigate this further

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从 testcontainers/kafka/init.py 和 testcontainers/core/docker_client.py 开始,重点关注 v4.13.1 与 v4.13.2 之间等待和端口映射方面的更改。在禁用 Ryuk 的 Windows 环境中复现所提供的 KafkaContainer 代码片段,然后验证容器能够启动,并且 get_bootstrap_server() 返回可用的 endpoint。

由索引模型根据 Issue 内容生成。

评估

技术栈
docker, kafka, python
领域
devops, testing-qa
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
冷清
描述清晰度
基本清楚
新手友好度
48/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。