Repository navigation
Running Training Scripts in WSL issues #361
Description
While setting up a new development/training environment I am having issues with the version of the scrips on the main branch.
Creating this issue as a place to hold the discussion.
Initially the items I am running into:
- When checking to see if the repository exists or not the
git ls-remotecall inrepo_is_reachabledoesn't include the User or PAT. Since I don't have my credential manager setup for WSL the call fails. I can put the $TOKEN_OWNER and $TEACHER_PAT into the call it is succeeds. - The version of
httpthat is installed in my WSL doesn't have the--quiteflag available and the call fails unless the flag is removed from the line.
My long term goal is to get the base training environment running in a container so that replicating the training material across my teams is easier, and makes setting up new machines easier.
I would love to collaborate with someone on this, or learn where I have made some mistakes in the setup.
The setup has changed a bit from the version we have been using, and I haven't actually trained in over a year and a half.
Activity
ppremk commentedon Apr 26, 2022
@mblack88 thank you for opening this issue, @dzeyelid has been working on a solution for this. @dzeyelid is there possibilities to collaborate with @mblack88 to test your solution?
dzeyelid commentedon Apr 27, 2022
Thank you @ppremk introducing me.
I got similar errors, so I'm creating a development container environment in my PR lefthandz-githubtraining/training-manual#8 and talking with @ppremk to improve it. (After finishing the improvement, I'll send a PR to this repository with the updates.)
In the environment, the
http --quietargument is available and your issue that is required username and password does not occur.If you would like to check the environment, you can fork my repository and run scripts on the branch
workspace.jessehouwing commentedon Oct 27, 2022
I upgraded my WSL to ubuntu-jammy, which fixes all issues, mine was on ubuntu 18LTS, but switching to 22LTS made my issues go away. I also repaired the codespaces to sun the correct version. See:
#378
steps to upgrade to ubuntu jammy:
To go from 18 to 22 I had to run these steps twice.