MSW (mock service worker) compatibility

[kieran-osgood]

Wondering if anyone is using testcontainers with MSW?

I have been using testcontainers:node to run my db during tests, I added MSW to mock some external urls and have been running into some issues (only on github actions) where the container no longer finishes setting up due to its health checks failing

Using MSW 2.12.1

I'm hoping I just am not writing the handlers regex here but I've tried a number of variations

I've added unhandled bypass to the server start

    http.all(/(^http:\/\/)?localhost(:\d+)?(\/)?.*$/, () => passthrough()),
    http.all(/(^http:\/\/)?127\.0\.0\.1(:\d+)?(\/)?.*$/, () => passthrough()),

I came to the above handlers from these logs which indicate they're trying to use localhost:5432

Failed to exec container with command "/bin/sh -c cat /proc/net/tcp* | awk '{print $2}' | grep -i :1538": Error: write EPIPE: 
Failed to exec container with command "/bin/sh -c nc -vz -w 1 localhost 5432": Error: write EPIPE: 
Failed to exec container with command "/bin/bash -c </dev/tcp/localhost/5432": Error: write EPIPE: 

[cristianrgreco]

We use it in the gcloud module:

testcontainers-node/packages/modules/gcloud/src/cloudstorage-emulator-container.test.ts

Lines 34 to 48 in d399600

	const server = setupServer();
	beforeAll(() => {
	server.listen({
	onUnhandledRequest: "bypass",
	});
	});
	beforeEach(() => {
	server.resetHandlers();
	});
	afterAll(() => {
	server.close();
	});

There used to be an issue with an older version of msw not playing well with the Docker socket, but that was fixed a few months back. If you update msw/Testcontainers I reckon everything is working.

[kieran-osgood]

I'll give that a try - thanks
In the end I resolved this by initialising msw first but wouldn't mind removing the workaround