sebarocks/docker-windows
1
0
Fork 0
mirror of https://github.com/dockur/windows.git synced 2026-05-06 14:41:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Added information about container memory limit handling by ballooning.

Browse source
This commit is contained in:
Luca De Petrillo 2026-05-05 16:54:36 +00:00
parent 958b50852d
commit 9a9b4ff11a
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
readme.md
View file

@ -174,7 +174,7 @@ kubectl apply -f https://raw.githubusercontent.com/dockur/windows/refs/heads/mas
By default, the VM is allocated the full amount of RAM configured via `RAM_SIZE` for its entire lifetime.
If you want the container to dynamically reclaim unused guest RAM based on host memory pressure, you can enable memory ballooning:
If you want the container to dynamically reclaim unused guest RAM based on host memory pressure, you can enable memory ballooning. It is also used to prevent the guest from exceeding the container's memory limit, even when the limit is changed at runtime:
```yaml
environment:
@ -205,6 +205,9 @@ kubectl apply -f https://raw.githubusercontent.com/dockur/windows/refs/heads/mas
> [!NOTE]
> Memory ballooning uses Linux PSI (`/proc/pressure/memory`) for progressive pressure detection. Between `BALLOONING_PSI_PRESSURE` and `BALLOONING_PSI_PRESSURE_MAX` the PSI ceiling linearly lowers the maximum balloon target from guest max memory down to the configured minimum. If PSI is unavailable (kernel lacks `CONFIG_PSI`), both thresholds are silently skipped and ballooning continues using host memory usage alone.
> [!WARNING]
> If the container memory limit is reduced at runtime below the guest VM's current memory usage, the container may be killed by the OOM killer if the ballooning driver cannot reclaim memory from the guest fast enough.
### How do I configure the username and password?
By default, a user called `Docker` is created and its password is `admin`.