-
Type:
Task
-
Resolution: Done
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Context
CSE prose tests require a build environment with libmongocrypt and its dependencies staged, which is currently a manual, error-prone local setup step. Create internal/test/docker/cse.Dockerfile, based on golang:1.26.4-trixie, that reproduces the driver's existing CI build steps (see Dockerfile#L5-L22) plus the libmongocrypt staging needed for CSE, so the container can be built and reused both locally and in CI. Wrap it in a testcontainers helper that starts the container and blocks it open (tail -f /dev/null) so a test process can run multiple commands against it over its lifetime, rather than a single one-shot RUN. We use a similar pattern in the compile-check logic.
Definition of done
- internal/test/docker/cse.Dockerfile added, based on golang:1.26.4-trixie, replicating Dockerfile#L5-L22 from the main repo Dockerfile, plus libmongocrypt staging
FROM golang:1.27.1-trixie COPY etc/install-libmongocrypt.sh /root/install-libmongocrypt.sh RUN cd /root && bash ./install-libmongocrypt.sh
- Image builds successfully (docker build succeeds, confirmed manually or via CI).
- internal/test/container gains a function that starts the CSE image via testcontainers-go and keeps it running (blocked on tail -f /dev/null) for the duration of a test.
- A test proves the container works end-to-end by executing go test -tags cse ./x/mongo/driver/mongocrypt inside the running container and asserting success.
Pitfalls
Not investigated
- duplicates
-
GODRIVER-4148 Hook up AWS SSO login and global container in TestMain
-
- Closed
-
- is duplicated by
-
GODRIVER-4174 Resolve codespell failure on internal/test/prose/go.sum
-
- Closed
-