Closed scottmuc closed 1 year ago
nvim
scary error about the colorscheme NeoSolarized
not being available. This doesn't break the script but it's jarring to read nevertheless.background light
to setup alacritty config in WindowsThe script went to completion!
Fun! Installing the fonts had a breaking change. A new release was made a couple weeks ago and they did some font renames (for sake of consistency). I appreciate the consistent name change, but I wish they could have duplicated the fonts and had a deprecation warning (though I have no idea how I would be able to see that warning):
~/workspace/infrastructure/pi ? cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
~/workspace/infrastructure/pi ? uname -a
Linux wsl 4.4.0-19041-Microsoft #2311-Microsoft Tue Nov 08 17:09:00 PST 2022 x86_64 x86_64 x86_64 GNU/Linux
Virtual Machine Platform
to Windows setup scriptIt appears docker cannot run. Looking at the kernel version of the previous repave (https://github.com/scottmuc/infrastructure/issues/54#issuecomment-1506770395) I can see I am running the old one. Running wsl --list --verbose
shows that my instance is running version 1.
It turns out the BIOS upgrade reset some other settings. I now believe that CSM
was something I may have disabled years ago! It also appears that SVM
reverted back to disabled. This BIOS setting enables/disables the CPU virtualization features.
After enabling the windows feature Virtual Machine Platform
and enabling SVM
in the BIOS, I was able to recreate a WSL instance with the up-to-date kernel version:
~ ? uname -a
Linux wsl 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
This was more interesting that I was expecting! The breaking change with the font was fun. Happy that I was able to fix up a couple things.
The Windows repave brought forward some interesting pieces to fix. Thankfully the scope was pretty small. The BIOS update resulting in WSL issues was an unexpected issue, but easy to resolve.
Overall, this was a nice repave to tie up a lot of loose ends with the Windows and WSL integrations.
Yay for Repaving!
As much as possible is documented inline in this issue template. In case of problems you may find help by viewing all the previous repave issues. Have fun!
Steps
[x] Run repave script from windows host
As an admin, run:
Set-ExecutionPolicy -ExectionPolicy RemoteSigned
Then run:
~/workspace/infrastructure/homedirs/windows/Repave-WSLInstance.ps
[x] Clone and run coalesce script
note this will need to be run twice for the python stuff to work
[x] Reboot WSL Instance
In order for
/etc/wsl.conf
to take effect we need to restart the WSL instance.wsl --shutdown Ubuntu
[x] Initalize 1Password
inialized-1password
[x] Load GPG Keys
[x] Bootstrap repository tools
Verification Steps
[x] Decrypt Repository
[x] Attempt DNS Change
[x] Configure PI (tests ansible)
[x] Clone all the repos (
mr checkout
)[x] Ensure
tldr
works[x] Ensure
deploy.sh
of goodenoughmoney.com works[x] Log OS release and kernel version