testcontainers-node icon indicating copy to clipboard operation
testcontainers-node copied to clipboard

Testcontainers is a NodeJS library that supports tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.

Results 110 testcontainers-node issues
Sort by recently updated
recently updated
newest added

Ryuk supports [verbose output via the `RYUK_VERBOSE` envvar](https://github.com/testcontainers/moby-ryuk/blob/e8ed9c9172b99aacc732cf0d09414e97e1294d64/main.go#L32). It should be possible to request this verbose output somehow. I would suggest automatically enabling verbose output when enabling verbose output via...

**Expected Behaviour** I should be able to extend the PostgreSqlContainer without issues as follows ```typescript public override async start() { return new StartedPostgreSqlContainer( await super.start(), this.database, this.username, this.password, ); }...

**Expected Behaviour** ```js const container = new RedisContainer('redis/redis-stack-server:7.2.0-v12') ``` This will fail because of the `redis-server` command. https://github.com/testcontainers/testcontainers-node/blob/9f7fd4eff5e6f05440016010964a78aa80557cb1/packages/modules/redis/src/redis-container.ts#L36-L39 As you can see from the docker images, `redis` uses `CMD [redis-server]`...

**Expected Behaviour** Able to initialize Couchbase as shown in examples - [Example 1](https://testcontainers.com/modules/couchbase/) - [Example 2](https://node.testcontainers.org/modules/couchbase/) ___ **Actual Behaviour** 1. Imports needed are not available. [These are the only available...

**Expected Behaviour** MySQL container should start and successfully connect to the Docker Desktop container ... **Actual Behaviour** starting the container throws an error: ```sh Error: (HTTP code 404) no such...

triage

**Expected Behaviour** Container should start up. **Actual Behaviour** ``` ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Error: No host port found for host IP ❯ resolveHostPortBinding ../../node_modules/.pnpm/[email protected]/node_modules/testcontainers/src/utils/bound-ports.ts:74:9 ❯ ../../node_modules/.pnpm/[email protected]/node_modules/testcontainers/src/utils/bound-ports.ts:55:46 ❯ Function.fromInspectResult ../../node_modules/.pnpm/[email protected]/node_modules/testcontainers/src/utils/bound-ports.ts:54:41 ❯...

triage

When trying to figure out why my containers weren't getting killed in my test suite I stumbled across a feature request for killing containers #716 . Looking into the resolution...

documentation