blog/fix-bashrc-not-executing-wsl/

[giscus[bot]]

blog/fix-bashrc-not-executing-wsl/

In case you haven't heard, I'm planning to do some livestreams in the near future which are focused on live development / building in the cloud. I'm working on a few ideas, but if you have any suggestions - please throw them my way! To prepare for this, I've recently spent some time making sure my local development environment is in order. Windows Terminal and Windows Subsystem for Linux are a couple of the key tools in my local development environment. Windows Subsystem for Linux is the focus for this post.

https://www.cloudwithchris.com/blog/fix-bashrc-not-executing-wsl/

[chrisreddington]

Want to join in the discussion? You can do that in two ways! You can either authorize the giscus app to post on your behalf using the GitHub OAuth flow. Alternatively, you can comment in GitHub Discussions directly if you'd prefer not to grant access to the giscus app.

Please keep the discussion on topic with the post.

[kfprugger]

I had the EXACT same problem. Thanks for posting this to your blog :-)

[chrisreddington]

Awesome, thanks kfprugger - glad to hear it solved the problem! Have you had any other challenges / topics you'd be interested to learn more about? :)

[mmarkus13]

TLDR: remove the ~/.bash_profile file.

mv ~/.bash_profile ~/.bash_profile.BAK

Thanks chrisreddington!

[Amondale]

my issue was similar; this article helped resolve it, so here was my thing: ~/.profile did exist but for whatever reason wasn't kicking over the .bashrc, so I used your IF statement to fix. There are a TON of miniscule differences between WSL2 and WSLg and 'systemd ubuntu'. Could be a recent do-release-upgrade to 22.04 in my WSL environment causred the change in .profile to happen. I assume this file is a runtime copy of /etc/profile?

[Amondale]

this is what my /etc/profile had in it (note not referring to ~/.bashrc but rather to /etc/bash.bashrc:

if [ -f /etc/bash.bashrc ]; then
  . /etc/bash.bashrc
fi

[chrisreddington]

Super, glad you were able to get this resolved @Amondale!

[obruehl]

Thanks chrisreddington! Works.

[chrisreddington]

@obruehl - An extremely delayed response on my part 🤣 But, thank you @obruehl - I'm glad it helped!

[zx8086]

Had the same issue due to following instructions for a Confluent Kafka installation... should have put the env vars in bashrc

[LewWadoo]

I also use WSL2 with Ubuntu. But for me, ~/.bashrc doesn't start before I explicitly call bash. I didn't have ~/.bash_profile, ~/.bash_login or ~/.profile, only /etc/profile. So I created ~/.bash_profile and placed my variable there, and it worked.

[niranjansm]

This was so useful. Spared me hours of debugging and got straight to the fix. Thank you.

[DanielAdeniji]

Chris Reddington:-

Gems of Software Engineering.

I never would have shared this if I were you.

This is one of those problems that stay millions in asylum wards.

Thank You for the sake of gentility and kindness.

Daniel

[bus0v]

Thank you so much! I was going insane trying to figure out what the problem was! Deleting the bash_profile fixed it!

[zenden2k]

Thank you, I had the same problem

[jeromemeichelbeck]

Thank you, same problem for me.