WSL App puts memory size on line above [wsl2] in .wslconfig

[ncotie]

Windows Version

Microsoft Windows [Version 10.0.26100.3323]

WSL Version

WSL version: 2.4.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

Linux version 5.15.167.4-microsoft-standard-WSL2 (root@f9c826d3017f) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Tue Nov 5 00:21:55 UTC 2024

Distro Version

Ubuntu 24.04.1 LTS

Other Software

No response

Repro Steps

Open the WSL Setting GUI app (as downloaded from App Store).
Change the setting for Memory Size under 'Memory and Processor'.
Observe .wslconfig file now have memory= on line2, without any [wsl2] heading above it.
Start WSL Ubuntu, observe in Ubuntu terminal:
"wsl: Unknown key 'memory' in C:\Users\xxx .wslconfig:2"

Expected Behavior

I'm new to this, but I don't think the GUI should be mishandling the .wslconfig file for something as basic as this?
That said, it does appear that WSL respects the changed max RAM setting.

Actual Behavior

As described above.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[benhillis]

I'm not able to reproduce this. Do you have other contents on your .wslconfig file?

[ncotie]

Thanks for the reply. I had reduced logical processors previously, but went back to defaults.
Right now, unchanged since the most recent WSL/Ubuntu restart, is:

  memory=17825792000
  [wsl2]
  [experimental]
  [wsl2]

If I understand correctly, that memory= line should be below a [wsl2] heading?

When I was trying to figure this out before opening the issue, I did attempt to remove the memory= line, using Notebook++, and saving it, but then WSL Settings App wrote it there again after setting the RAM size again, so it didn't appear to me to be a one-time artefact.