testcontainers-go
testcontainers-go copied to clipboard
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 p...
**Describe the bug** I started to move from using an already-running database to using postgres in a container via testcontainers-go, and when I did, the logs that normally stream to...
```dockerfile # Dockerfile EXPOSE 11211 CMD ["memcached"] ``` ```golang // Code port := "11211/tcp" rq := testcontainers.ContainerRequest{ Image: "memcached:1.6.10", ExposedPorts: []string{port}, WaitingFor: wait.ForListeningPort(nat.Port(port)), } memcachedC, err := testcontainers.GenericContainer(context.Background(), testcontainers.GenericContainerRequest{ ContainerRequest:...
https://github.com/testcontainers/testcontainers-go/issues/285 add constructor that takes []io.Reader
**Describe the bug** My testcontainer runs fine directly on host. This case is to run test inside a docker container. I managed to add some parameters when starting docker so...
Hi, I'd like to be able to send all the stdout or stderr for a compose `.Invoke()` to an `io.Writer` of my choosing. Is there a way to do that...
Containers created and started by testcontainers-go through Docker Compose are not guaranteed to be cleaned up (and this is something I personally observed when running the testcontainers-go test suite on...
**The Issue** I'm attempting to get my project setup with testcontainers to test my database code. I'm using the postgres:11.7 image and everytime I try to run the test code,...
**Describe the bug** The `ProviderType.GetProvider()` function creates a docker client, but never closes it, which leads to a leaking connection. Similar to https://github.com/testcontainers/testcontainers-go/issues/319 **To Reproduce** Use following test: ```go package...