chore(test): make the container suite runnable under colima - #21
Merged
Merged
Conversation
ekalinin
force-pushed
the
docs/spec-code-alignment
branch
from
August 17, 2026 19:26
92fe9a7 to
aae0f6c
Compare
ekalinin
force-pushed
the
chore/colima-container-tests
branch
from
August 17, 2026 19:26
cd98feb to
1406953
Compare
ekalinin
force-pushed
the
docs/spec-code-alignment
branch
from
August 17, 2026 19:35
aae0f6c to
f55f04a
Compare
ekalinin
force-pushed
the
chore/colima-container-tests
branch
from
August 17, 2026 19:35
1406953 to
4b0d719
Compare
testcontainers does not read the docker CLI context, so on a colima host it reported "rootless Docker not found" and every integration test failed before starting a container. The target now spells out both variables it needs when the current context is colima: DOCKER_HOST is the host-side socket it connects to, and TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE is that same socket as seen inside the VM, which is what its reaper container bind-mounts. Both stay empty on Docker Desktop and in CI, where the default socket is already correct for each. Also stops logging a draining 503 as an ERROR. It is expected operation and would fill the log on every rolling deploy; an unreachable database is already logged where it is detected, with the driver detail the response deliberately drops.
ekalinin
force-pushed
the
docs/spec-code-alignment
branch
from
August 18, 2026 09:47
f55f04a to
64cdda2
Compare
ekalinin
force-pushed
the
chore/colima-container-tests
branch
from
August 18, 2026 09:47
4b0d719 to
2a04130
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Running the container suite
testcontainers does not read the docker CLI context, so on a colima host it reported
rootless Docker not foundand the whole integration suite failed before starting a single container.Two variables are needed, and both:
DOCKER_HOST- the host-side socket it connects to;TESTCONTAINERS_DOCKER_SOCKET_OVERRIDE- that same socket as seen inside the VM, because its reaper container bind-mounts it. With onlyDOCKER_HOSTset, Docker tries to mount the host-side path and fails withmkdir ... operation not supported.make test-containerssupplies both when the current docker context iscolima. On Docker Desktop and in CI they stay empty: there the default socket is already correct both for connecting and for mounting.Log level for a draining 503
A rejection during drain was logged as
ERROR. It is expected operation, and every rolling deploy would fill the log with it. Only the internal-error bucket is logged now; an unreachable database is already logged where it is detected, with the driver detail that the response deliberately drops.Verification
make test-containerspasses with no manual environment variables: 8/8 tests against real Redis, PostgreSQL 18, MySQL 8.4 and MinIO.