fix: escape the container name in the Docker name filter

[jcmfernandes]

What does this PR do?

Quotes the name filter of the Docker container list API is a regular expression, so metacharacters in a container name are interpreted instead of matched literally.

Why is it important?

A lookup for "cache.1" also matches "cacheX1", and ReuseOrCreateContainer can reuse the wrong container.

Since container names may only include ^[a-zA-Z0-9][a-zA-Z0-9_.-]+$ char . (dot) is the only metacharacter reachable through a legal container name.

Related issues

Not related to, by raised in #3051 by an LLM code review.

[netlify]

✅ Deploy Preview for testcontainers-go ready!

Name	Link
🔨 Latest commit	4365cfa
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-go/deploys/6a74532322e70c0008794e16
😎 Deploy Preview	https://deploy-preview-3837--testcontainers-go.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d8aa7055-c59e-448b-a92f-aadd5a454c45

📥 Commits

Reviewing files that changed from the base of the PR and between 2f869d6 and 4365cfa.

📒 Files selected for processing (2)

• docker.go
• docker_test.go

🚧 Files skipped from review as they are similar to previous changes (2)

• docker_test.go
• docker.go

---

Summary by CodeRabbit

• Bug Fixes

  • Improved container-name matching so special characters are treated literally, preventing incorrect matches.

• Tests

  • Added coverage verifying accurate lookups for names containing punctuation.

Walkthrough

The Docker provider now escapes container names before building its name filter regex. A regression test confirms that periods are treated literally.

Changes

Container name matching

Layer / File(s)	Summary
Escape and validate name filter docker.go, docker_test.go	findContainerByName now applies regexp.QuoteMeta to the requested name. The regression test confirms that test.1 does not match testX1.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

I’m a rabbit checking each name,
A dot stays a dot in the matching game.
Literal strings guide the way,
Tests keep wildcards away.
Hop, hop—safe filters today!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: escaping container names in the Docker name filter.
Description check	✅ Passed	The description explains the Docker regex issue, its impact, and the reason for escaping container names.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.

[jcmfernandes]

Rebased.

[mdelapenya]

LGTM, thanks