-
-
Notifications
You must be signed in to change notification settings - Fork 271
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]: Unable to configure memory limit #1090
Comments
This is not an issue in Testcontainers. Unfortunately, this is a limitation of Docker and is documented.
You will find more information in the related pull request as well (moby/moby#41168). |
I've set value to 2GB (see the code). Are you sure it's not the testcontainer proxy container issue? |
Nope, you did not. You set it to 2MB. According to the API docs the unit is bytes.
|
🤦 |
Testcontainers version
3.7.0
Using the latest Testcontainers version?
Yes
Host OS
Windows
Host arch
x64
.NET version
8.0
Docker version
Client: Cloud integration: v1.0.35+desktop.5 Version: 24.0.7 API version: 1.43 Go version: go1.20.10 Git commit: afdd53b Built: Thu Oct 26 09:08:44 2023 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.26.1 (131620) Engine: Version: 24.0.7 API version: 1.43 (minimum version 1.12) Go version: go1.20.10 Git commit: 311b9ff Built: Thu Oct 26 09:08:02 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.25 GitCommit: d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f runc: Version: 1.1.10 GitCommit: v1.1.10-0-g18a0cb0 docker-init: Version: 0.19.0 GitCommit: de40ad0
Docker info
What happened?
Using
HostConfig.Memory
to configure memory limit gets me an error:Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: