No /etc/profile or ~/.bashrc env vars available when executing a command as "wsl <cmd>"

[KarelChanivecky]

Windows Version

Version 10.0.19045.3693

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

SETUP
1- In distro, add env var to /etc/profile. Example: export VAR1=1
2- In distro, add env var to ~/.bashrc. Example: export VAR2=2

TEST 1
1- enter the distro using "wsl" cmd
2- Run "env" cmd

TEST 2
1- from Windows command line run "wsl env"

TEST 3
1- from Windows command line run 'wsl bash --login -c "env"'

Expected Behavior

TEST 1
Both variables are present in the environment.
* The .bashrc var is expected, as the SHELL env var states that bash is the current shell, at least in my distro

TEST 2
Both variables are present in the environment.
* The .bashrc var is expected, as the SHELL env var states that bash is the current shell, at least in my distro

TEST 3
Both variables are present in the environment.

Actual Behavior

TEST 1
Both variables are present in env.

TEST 2
Neither variable is present in env.

TEST 3
Only the var set in /etc/profile is present in env

Diagnostic Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Set Windows environment variables directly in wsl shell without modifying bash environment (#6747), similarity score: 0.75

Closed similar issues:

• Running wsl <command> from windows command line is missing environment variables (#7053), similarity score: 0.81
• "wsl.exe --distribution Ubuntu --exec /bin/sh -c" does't load any $PATH variables set in ~/.profile or ~/.bashrc or ~/.bash_profile (#7861), similarity score: 0.78
• run *.cmd from wsl shell (#4547), similarity score: 0.78
• Use wsl path in cmd (#1861), similarity score: 0.78
• Unable to push env vars to WSL on startup (#4613), similarity score: 0.77
• The environment PATH while running inside WSL vs. running via bash -c differs (#2634), similarity score: 0.76
• WSL ignores environment path (#8976), similarity score: 0.76
• Set path environment variable in WSL-Ubuntu (#3639), similarity score: 0.76
• wsl execute only bash commands and not windows options (#4937), similarity score: 0.75

You can give me feedback by thumbs upping or thumbs downing this comment.

[OneBlue]

/dupe #7861

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!