testcontainers / testcontainers/testcontainers-python
Containers fail to start: mssql/win11, mssql/m1, mssql with different port (not intended to work), postgres/win10, mariadb/win11, oracle
Open
Nobody has claimed this yet.
👀 requires attention
🔀 requires triage
- Dominant language
- Python
- Stars
- 2.3k
- Forks
- 386
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
I'm unable to run the SqlServerContainer. After creating the MSSQL container, it gets stuck at the "waiting to be ready" state and does not proceed further.
To Reproduce
from sqlalchemy import create_engine, text
from testcontainers.mssql import SqlServerContainer
with SqlServerContainer() as mssql:
engine = create_engine(mssql.get_connection_url())
with engine.begin() as connection:
version = connection.execute(text("select @@VERSION"))
Runtime environment
Docker Desktop 4.19.0 (106363)
Windows 11
Python 3.9
testcontainers==3.7.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the SqlServerContainer example with Docker Desktop, Windows 11, Python 3.9, and testcontainers 3.7.1, then inspect the container's readiness behavior. Compare the MSSQL failure with the other environments named in the title; done means the affected containers leave the waiting state and the SQLAlchemy connection succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python, sqlalchemy
- Domain
- databases, devops, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100