Running Home Assistant via wslc exits abnormally when adding the -v parameter

[edjia]

Windows Version

10.0.26200.8737

WSL Version

2.9.3.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.18.35.2-1

Distro Version

No response

Other Software

Repro Steps

run command

wslc run  --rm -v d:\wslc\ha:/config -p 8123:8123 --name=ha homeassistant/home-assistant

Expected Behavior

wslc run  --rm  -p 8123:8123 --name=ha homeassistant/home-assistant

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun home-assistant (no readiness notification) s6-rc: info: service legacy-services successfully started

Actual Behavior

s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun home-assistant (no readiness notification) s6-rc: info: service legacy-services successfully started Traceback (most recent call last): File "<frozen runpy>", line 203, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/__main__.py", line 227, in <module> sys.exit(main()) ~~~~^^ File "/usr/src/homeassistant/homeassistant/__main__.py", line 189, in main with runner.ensure_single_execution(config_dir) as single_execution_lock: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^ File "/usr/local/lib/python3.14/contextlib.py", line 141, in __enter__ return next(self.gen) File "/usr/src/homeassistant/homeassistant/runner.py", line 146, in ensure_single_execution _write_lock_info(lock_file) ~~~~~~~~~~~~~~~~^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/runner.py", line 67, in _write_lock_info lock_file.truncate() ~~~~~~~~~~~~~~~~~~^^ PermissionError: [Errno 13] Permission denied [09:56:51] INFO: Home Assistant Core finish process exit code 1 [09:56:51] INFO: Home Assistant Core service shutdown s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it

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-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

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

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[edjia]

WslLogs-2026-07-03_18-37-27.tar.gz

[github-actions]

Diagnostic information

Detected appx version: 2.9.3.0

[OneBlue]

@edjia: It's looking like the root cause of the issue is: PermissionError: [Errno 13] Permission denied [09:56:51].

Could you share an strace so we can see which exact file access is giving this error ?