-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: 1.18.1 to 1.18.3 gives Out Of Heap Memory exception for DockerComposeContainer #7239
Comments
i would like to contribute this issue, kindly assign this to me |
This was caused by 00a509c |
is your docker-compose file that big? |
If I interpret the code correctly, you are trying to copy the whole directory where the compose file is located into the container causing the oom: from testcontainers-java/core/src/main/java/org/testcontainers/containers/ContainerisedDockerCompose.java Line 33 in 595076c
and onwards |
Thanks! good catch! I didn't fall into that because the docker-compose files are inside different folders. I need to figure out how to fix it properly. The workaround would be to move the docker-compose.yml to a folder |
Depending on what your As workaround use |
Still have issue on 1.19.0. Only working with 1.18.0 |
So sounds like two work-arounds so far
|
@frankjkelly - fancy meeting you here, long time no see :). |
Hey there @Michael-Rosa-Imprivata - wow fancy meeting you here!? Hope all is well. |
FYI I just tried work-around of moving the
|
Yea same here Frank. Work arounds are not doing the trick. We decided to revert back to the previous working version as well for now. |
@Michael-Rosa-Imprivata just out of interest So That sounds odd (or different issue), since the LocalDockerCompose doesn't copy, compared to ContainerisedDockerCompose in GenericContainer. Could you paste stacktrace/output/code snippet, when using |
Hi, Exemple in gradle
|
|
@eugene-kuntsevich https://java.testcontainers.org/modules/docker_compose/#local-compose-mode In short, it executes |
When I try
Is there a second part to this workaround that is needed? |
Like explained here https://java.testcontainers.org/modules/docker_compose/, it means that testcontainers use the local binary of docker compose instead of using a docker image with docker compose inside. |
Any update on this? |
Any update? |
Is there any workaround for this? |
#1348 is i think the most highly relevant piece - if copying the files is really non-negotiable (maybe making this bind vs copy behavior configurable is agreeable to testcontainers-java maintainers?) then implementing |
Hi @alexanderankin , thanks a lot ! |
#2864 was replacing some in-memory buffering (ByteArrayOutputStream) with a temp file. Not sure if it still is relevant. |
#8409 has been merged and it should fix the issue. |
Module
Core
Testcontainers version
1.18.1 to 1.18.3
Using the latest Testcontainers version?
Yes
Host OS
MacOS
Host Arch
x86 Intel Core i7
Docker version
$ docker version Client: Cloud integration: v1.0.31 Version: 23.0.5 API version: 1.42 Go version: go1.19.8 Git commit: bc4487a Built: Wed Apr 26 16:12:52 2023 OS/Arch: darwin/amd64 Context: default Server: Docker Desktop 4.19.0 (106363) Engine: Version: 23.0.5 API version: 1.42 (minimum version 1.12) Go version: go1.19.8 Git commit: 94d3ad6 Built: Wed Apr 26 16:17:45 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.20 GitCommit: 2806fc1057397dbaeefbea0e4e17bddfbd388f38 runc: Version: 1.1.5 GitCommit: v1.1.5-0-gf19387a docker-init: Version: 0.19.0 GitCommit: de40ad0
What happened?
When upgrading only test containers from 1.18.0 to 1.18.1 got heap error on startup of my Docker Compose based Integration tests.
Also tried 1.18.3.
Relevant log output
Additional Information
No response
The text was updated successfully, but these errors were encountered: