contribution/compass
testcontainers/testcontainers-go

Testcontainers for Go

2 signals · 2 observation events

Open repository ↗

Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically define containers that should be run as part of a test and clean up those resources when the test is done.

4.9K stars628 forksGoMITautomationdockergogolanghacktoberfesttestcontainerstestcontainers-gotestingkeyword: Testcontainers
PROJECT NEWS

Release, roadmap, and discussion

All news →
testcontainers/testcontainers-go

Testcontainers for Go

Developer Infrastructure
Latest stable

v0.44.0

v0.44.0
  • 🔒 Security
  • security: fix Dependabot alerts for grpc and OTel (#3835) @mdelapenya
  • 🚀 Features
  • feat: allow overriding the session ID (#3051) @jcmfernandes
  • feat: add Azure SQL Edge module (#3787) @mdelapenya
Original release notes ↗

Publicly indicated next

  • No public prerelease or open milestone found.

Prereleases and milestones indicate public plans; they are not delivery commitments.

Observation trail

  1. discoveredinitial snapshot
  2. changedinitial snapshot
2 shown
issue

[Feature]: Honor DOCKER_HOST scheme when launching Ryuk (TCP/TLS daemon support)

## Problem When `DOCKER_HOST` points at a TCP daemon (`tcp://...` or `https://...`), testcontainers-go itself talks to that endpoint correctly — but Ryuk gets launched with a hard-coded bind-mount of the host Docker socket: ```go // reaper.go ~line 385 hc.Binds = []string{dockerHostMount + ":/var/run/docker.sock"} ``` This breaks any setup where the test pro

importance 5@BorisTyshkevichopenOriginal evidence ↗
pull request

fix: return reaper handshake errors

This supersedes #3828. The original PR was automatically closed after I accidentally deleted my fork ## Related issues - Closes #3827 ## What does this PR do? This PR makes `Reaper.connect` perform the Ryuk handshake synchronously before returning a successful connection. If the handshake fails, the connection is closed and the handshake error is returned to

importance 1@drawliinopenOriginal evidence ↗