-
Notifications
You must be signed in to change notification settings - Fork 41
docker doesn't use memory or CPU options #145
Comments
This needs an issue in moby/moby. Will probably require changes to moby/moby as well as opengcs |
Leave it here for now. It's already on my list. |
It would be great if the move to LCOW allowed enabling dynamic memory for Linux containers. |
Good news :) Containers with Hyper-V isolation already allocate memory on-demand so it's more or less comparable to dynamic memory. This option puts a limit on the max memory size which is enforced by the hypervisor. You can see this behavior by looking at the memory usage of vmmem processes on the host. Those are a wrapper to hold the memory used by the container |
ping @jhowardmsft - is this still in the works? do you have an issue in moby/moby yet? |
Is this change as simple as adding the the following code snippet to
|
OK, the previous code does not work. However, if anyone is in need of this, adding a hardcoded value to the docker source code works. Add |
@yusuf-gunaydin I'm going to try this out... have you looked into possibly grabbing the |
@yusuf-gunaydin thanks for the tip, seems to work :) |
@fizxmike If I recall correctly I have tried the code I posted above, but it didn't work either for CPU or memory or neither. As I needed them both, I hardcoded the CPU and memory values. By the way CPU is also limited to 2 cores, if anyone needs the information. I couldn't find a good way to debug docker sources. Println debugging and recompiling the whole source every time a small change is made prevents me from trying more. |
Is this still being implemented? I'm running Docker Edge PS C:\Users\C740763> docker info |
Hi, Is there an estimate on when this will be fixed? |
There is a PR up in Moby at moby/moby#37296 ... but it's unclear how close to approval it is. Some folks have built from source with success. |
@jhowardmsft - None of these asks are OpenGCS specific and indeed the platform already supports them. Its just a config issue in Docker correct? Can we close this to avoid confusion? Or am I missing something fundamental here? |
@jterry75 Yes, I'm closing it here. The fix needs to go in moby, although maintainers there are not accepting it. There have been several PR attempts in moby to fix. |
For example, if I try running
mssql-server-linux
image with-m=4g
, I get this errorsqlservr: This program requires a machine with at least 3250 megabytes of memory.
The text was updated successfully, but these errors were encountered: