Kubernetes/k8s 開發筆記 - 在 Macbook M1 Pro 安裝 minikube, qemu, socket_vmnet @ macOS 13.5.1

之前略知 Apple M1 架構，對於使用一些軟體服務會卡卡，終於來體驗一下。原先在考慮依照官網的簡介:

minikube start - minikube.sigs.k8s.io/docs/start/

後來決定都靠 Homebrew 來管理，安裝流程：

% sw_vers

ProductName: macOS

ProductVersion: 13.5.1

BuildVersion: 22G90

% brew --version

Homebrew 4.1.7

% brew install qemu socket_vmnet minikube

Error: Cannot install in Homebrew on ARM processor in Intel default prefix (/usr/local)!

Please create a new installation in /opt/homebrew using one of the

"Alternative Installs" from:

  https://docs.brew.sh/Installation

You can migrate your previously installed formula list with:

  brew bundle dump

% eval "$(/opt/homebrew/bin/brew shellenv)"

% brew install qemu socket_vmnet  minikube

...

socket_vmnet requires root privileges so you will need to run

  `sudo /opt/homebrew/opt/socket_vmnet/socket_vmnet` or `sudo brew services start socket_vmnet`.

You should be certain that you trust any software you grant root privileges.

socket_vmnet is keg-only, which means it was not symlinked into /opt/homebrew,

because Homebrew's bin directory is often writable by a non-admin user.

If you need to have socket_vmnet first in your PATH, run:

  echo 'export PATH="/opt/homebrew/opt/socket_vmnet/bin:$PATH"' >> ~/.zshrc

To start socket_vmnet now and restart at startup:

  sudo brew services start socket_vmnet

Or, if you don't want/need a background service you can just run:

  /opt/homebrew/opt/socket_vmnet/bin/socket_vmnet --vmnet-gateway\=192.168.105.1 /opt/homebrew/var/run/socket_vmnet

...

% sudo brew services start socket_vmnet

Service `socket_vmnet` already started, use `brew services restart socket_vmnet` to restart.

% minikube start --driver=qemu --network socket_vmnet

😄  minikube v1.31.2 on Darwin 13.5.1 (arm64)

✨  Using the qemu2 driver based on user configuration

👍  Starting control plane node minikube in cluster minikube

🔥  Creating qemu2 VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...

🐳  Preparing Kubernetes v1.27.4 on Docker 24.0.4 ...

    ▪ Generating certificates and keys ...

    ▪ Booting up control plane ...

    ▪ Configuring RBAC rules ...

🔗  Configuring bridge CNI (Container Networking Interface) ...

    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5

🔎  Verifying Kubernetes components...

🌟  Enabled addons: default-storageclass, storage-provisioner

🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

% minikube status

minikube

type: Control Plane

host: Running

kubelet: Running

apiserver: Running

kubeconfig: Configured

% minikube stop  

✋  Stopping node "minikube"  ...

🛑  1 node stopped.

% minikube status

minikube

type: Control Plane

host: Stopped

kubelet: Stopped

apiserver: Stopped

kubeconfig: Stopped

然後重開機後，進入 zsh 環境時，需要重新做一點設定，就看個人的習慣要不要安置自動化了：

% minikube status

zsh: command not found: minikube

% eval "$(/opt/homebrew/bin/brew shellenv)"

% minikube status

🤷  Profile "minikube" not found. Run "minikube profile list" to view all profiles.

👉  To start a cluster, run: "minikube start"

% minikube start --driver=qemu --network socket_vmnet

😄  minikube v1.31.2 on Darwin 13.5.1 (arm64)

✨  Using the qemu2 driver based on user configuration

👍  Starting control plane node minikube in cluster minikube

🔥  Creating qemu2 VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...\ OUTPUT: 

ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused

🔥  Deleting "minikube" in qemu2 ...

🤦  StartHost failed, but will try again: creating host: create: creating: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1

🔥  Creating qemu2 VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...\ OUTPUT: 

ERROR: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused

😿  Failed to start qemu2 VM. Running "minikube delete" may fix it: creating host: create: creating: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1

❌  Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: creating host: create: creating: Failed to connect to "/opt/homebrew/var/run/socket_vmnet": Connection refused: exit status 1

╭───────────────────────────────────────────────────────────────────────────────────────────╮

│                                                                                           │

│    😿  If the above advice does not help, please let us know:                             │

│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │

│                                                                                           │

│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │

│                                                                                           │

╰───────────────────────────────────────────────────────────────────────────────────────────╯

% sudo brew services restart socket_vmnet

Password:

Stopping `socket_vmnet`... (might take a while)

==> Successfully stopped `socket_vmnet` (label: homebrew.mxcl.socket_vmnet)

Warning: Taking root:admin ownership of some socket_vmnet paths:

  /opt/homebrew/Cellar/socket_vmnet/1.1.2/bin

  /opt/homebrew/Cellar/socket_vmnet/1.1.2/bin/socket_vmnet

  /opt/homebrew/opt/socket_vmnet

  /opt/homebrew/opt/socket_vmnet/bin

This will require manual removal of these paths using `sudo rm` on

brew upgrade/reinstall/uninstall.

==> Successfully started `socket_vmnet` (label: homebrew.mxcl.socket_vmnet)

% minikube delete

% minikube start --driver=qemu --network socket_vmnet

😄  minikube v1.31.2 on Darwin 13.5.1 (arm64)

✨  Using the qemu2 driver based on user configuration

👍  Starting control plane node minikube in cluster minikube

🔥  Creating qemu2 VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...

🐳  Preparing Kubernetes v1.27.4 on Docker 24.0.4 ...

    ▪ Generating certificates and keys ...

    ▪ Booting up control plane ...

    ▪ Configuring RBAC rules ...

🔗  Configuring bridge CNI (Container Networking Interface) ...

    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5

🔎  Verifying Kubernetes components...

🌟  Enabled addons: storage-provisioner, default-storageclass

🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

% minikube status

minikube

type: Control Plane

host: Running

kubelet: Running

apiserver: Running

kubeconfig: Configured

上述是因為筆電重啟後時，碰到 socket_vmnet 問題，最後就先試著把整套環境刪除 (minikube delete) 而重來，而後續常規的用法：

% eval "$(/opt/homebrew/bin/brew shellenv)"

% sudo brew services restart socket_vmnet  

Warning: Taking root:admin ownership of some socket_vmnet paths:

  /opt/homebrew/Cellar/socket_vmnet/1.1.2/bin

  /opt/homebrew/Cellar/socket_vmnet/1.1.2/bin/socket_vmnet

  /opt/homebrew/opt/socket_vmnet

  /opt/homebrew/opt/socket_vmnet/bin

This will require manual removal of these paths using `sudo rm` on

brew upgrade/reinstall/uninstall.

==> Successfully started `socket_vmnet` (label: homebrew.mxcl.socket_vmnet)

% minikube start --driver=qemu --network socket_vmnet

😄  minikube v1.31.2 on Darwin 13.5.1 (arm64)

✨  Using the qemu2 driver based on existing profile

👍  Starting control plane node minikube in cluster minikube

🔄  Restarting existing qemu2 VM for "minikube" ...

🐳  Preparing Kubernetes v1.27.4 on Docker 24.0.4 ...

🔗  Configuring bridge CNI (Container Networking Interface) ...

🔎  Verifying Kubernetes components...

    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5

🌟  Enabled addons: storage-provisioner, default-storageclass

🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

% minikube status

minikube

type: Control Plane

host: Running

kubelet: Running

apiserver: Running

kubeconfig: Configured

Node.js 筆記 - 使用 Puppeteer 抓取網頁上的圖片內容並靠 Tesseract 分析圖片上的文字 (OCR) @ macOS 13.5.1, node v20.5.1, tesseract v5.3.2

剛好有同好在詢問如何處理認證碼的事，就順手複習一下 node.js 與 Puppeteer 動態爬網頁，並且把認證碼圖片存起來，在靠 Tesseract 分析上述的文字。

以前略知 光學字元辨識(OCR) 的方式，但一直沒實戰，這次就順手摸一下：github.com/changyy/node-puppeteer-with-tesseract-tool

目前只單純練一下功，還不到實際使用的地步，因為 Tesseract 分析上仍有精準度問題，純做個小工具方便把玩。此程式碼只提供快速定位到 <img> (getElementById)  的方式，接著動態存成圖片，再呼叫工具分析它。

此外，已經存在本機了，後續也能靠 tesseract 指令反覆測試參數。

安裝：

% sudo port install tesseract tesseract-eng tesseract-chi-tra tesseract-chi-sim 

% sw_vers
ProductName: macOS
ProductVersion: 13.5.1
BuildVersion: 22G90
% tesseract --version
tesseract 5.3.2
leptonica-1.82.0
libgif 5.2.1 : libjpeg 8d (libjpeg-turbo 2.1.5.1) : libpng 1.6.40 : libtiff 4.5.1 : zlib 1.2.11 : libwebp 1.3.1 : libopenjp2 2.5.0
Found SSE4.1
Found libarchive 3.6.2 zlib/1.2.11 liblzma/5.4.1 bz2lib/1.0.8 liblz4/1.9.4 libzstd/1.5.4
Found libcurl/8.1.2 SecureTransport (LibreSSL/3.3.6) zlib/1.2.11 nghttp2/1.51.0

使用：

% nvm use v20
Now using node v20.5.1 (npm v9.8.0)
% npm install
% npm run main
> main
> node main.js
Usage> node /private/tmp/node-puppeteer-with-tesseract-tool/main.js "WebURL" "ImageObjectID"
% node main.js
Usage> node /private/tmp/node-puppeteer-with-tesseract-tool/main.js "WebURL" "ImageObjectID"

測試：

% node main.js 'https://xxx/login' 'verifyImgCode'
[INFO] WebURL: "https://xxx/login", The id of the DOM <img>: "verifyImgCode"

  Puppeteer old Headless deprecation warning:
    In the near future `headless: true` will default to the new Headless mode
    for Chrome instead of the old Headless implementation. For more
    information, please see https://developer.chrome.com/articles/new-headless/.
    Consider opting in early by passing `headless: "new"` to `puppeteer.launch()`
    If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.

on.domcontentloaded
on.framenavigated: about:blank
on.load
...
page.screenshot
browser.close
tesseract.recognize result:  058B47

練精準度：

% tesseract /tmp/verify-code.png stdout -c tessedit_char_whitelist=0123456789

[macOS] 從 Macbook 遠端登入 Windows 筆電並使用 PowerShell 工作環境 @ macOS 13.2.1

由於想善用 Windows 筆電的資源（算力），先來試試看能不能打通 macOS command line 遠端登入進 Windows 11 筆電。查了一下資料，看來真的也有人有這種需求 XD

原理：

1. Windows 11 安裝 OpenSSH Server
• 微軟官方文件 - 安裝 OpenSSH 用戶端和伺服器進行 Windows
2. macOS 安裝 PowerShell Core 資源 (非必要)
• github.com/PowerShell/PowerShell

其中一還滿常見，二就有點怕怕，所幸資源算是微軟提供（？），有興趣可以裝 pkg 檔案，裝完在 macos command line 用 pwsh 指令就切換到 PowerShell 工作環境，目前只需做 (1) 就能完成需求，以下是在 Windows 11 筆電下運行指令，建議在上述微軟官方文件上複製使用，在此純做筆記：

PS C:\Users\user> Get-WindowsCapability -Online | Where-Object Name -like 'OpenSSH*'

Name  : OpenSSH.Client~~~~0.0.1.0

State : Installed

Name  : OpenSSH.Server~~~~0.0.1.0

State : NotPresent

PS C:\Users\user> ssh -V

OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3

PS C:\Users\user> Add-WindowsCapability -Online -Name OpenSSH.Server~~~~0.0.1.0

Path          :

Online        : True

RestartNeeded : False

PS C:\Users\user> Start-Service sshd

PS C:\Users\user> Set-Service -Name sshd -StartupType 'Automatic'

PS C:\Users\user> if (!(Get-NetFirewallRule -Name "OpenSSH-Server-In-TCP" -ErrorAction SilentlyContinue | Select-Object Name, Enabled)) {

>>     Write-Output "Firewall Rule 'OpenSSH-Server-In-TCP' does not exist, creating it..."

>>     New-NetFirewallRule -Name 'OpenSSH-Server-In-TCP' -DisplayName 'OpenSSH Server (sshd)' -Enabled True -Direction Inbound -Protocol TCP -Action Allow -LocalPort 22

>> } else {

>>     Write-Output "Firewall rule 'OpenSSH-Server-In-TCP' has been created and exists."

>> }

Firewall rule 'OpenSSH-Server-In-TCP' has been created and exists.

PS C:\Users\user> ssh localhost

user@localhost's password:

如此筆電重啟後，也會自動啟動 OpenSSH Server 。而 macOS 要遠端進去一樣把它當成 linux server 即可，靠 ssh 加上帳密遠端登入。

另外，常會使用 ping 來查看機器健康情況，而 Windows 11 默認關閉（也是滿好的資安規劃），在此要人工開啟：

系統 -> 隱私權與安全性 -> Windows 安全性 -> 防火牆與網路保護 -> 進階設定 -> 輸入規則 ->  核心網路診斷 - ICMP 回應要求 -> 啟動

可以自行依照需求開啟全部 ICMP 回應或部分情境。 

最後，莫忘筆電的電源節源設計，預設應該是 5分鐘就會進入休眠，可以把它調整成插電就永不進入休眠，以及要衝刺算力也可以調整電源策略。

我有酒，你有故事嗎？

最近不少事務變動，在公司待的年數也增加不少，在這多頭的年裡，經歷過同事加入與主動離職，這次開始經手組員離職的流程，回顧著被離職同事的工作項目，也得重新安排給其他同事接手。在管理團隊上也體驗完全套：招募成員、成員主動離去與成員被動離去 Orz

想著想著，就像木曜四超玩的畢業典禮：

對於被離職的同事，這樣的歲數上有著許多可選之路，恰恰好被推動去選擇其他擺盪許久的機會，雖然被離開肯定不是好事，但這樣的故事發展卻也不是壞事的。

想想好友們換房換車的繼續行動、出國的出國、皮拉提斯的皮拉提斯，大家還是持續過得很精彩的。

這陣子跟幾位朋友分享彼此近況，同輩的有那種越來越收斂在自身的狀態，實在是有太多不可控的項目，包括工作的變異、親人的分離、退化的健康，漸漸地「關我屁事」可能也真的成了主流？讓自己的心情專注在自身了。

時間依舊是稀缺，當年用第24個夏天來做個足跡紀錄，現在可能要變成“人生還有多少個暑假可用？”了，看在學生時期認識的教授開始退休，還有把刷 leetcode 當作娛樂的，努力譜曲著自己的故事。

建置 DSM 7.2 可運行的 tmux 工具 @ Synology DS723+, AMD Ryzen R1600, DSM 7.2 ToolChain

前幾天升級 Synology NAS 後，之前用 DSM 7.1 toolchain 編譯出的 tmux ，在 DSM 7.2 運行出包，一跑就顯示 server exited unexpectedly，通常解法是清除 /tmp 下跟 tmux 相關的檔案目錄，只是依舊沒解決問題 Orz 就試試看在 Ubuntu 22.04 + DSM 7.2 ToolChain 重新編譯一下，下載 ToolChain 資訊：

• help.synology.com/developer-guide/compile_applications/download_dsm_tool_chain.html
• archive.synology.com/download/ToolChain/toolchain
• global.synologydownload.com/download/ToolChain/toolchain/7.2-63134/AMD%20x86%20Linux%204.4.302%20%28r1000%29/r1000-gcc1220_glibc236_x86_64-GPL.txz

由於 DS723+ 的處理器是 AMD Ryzen R1600 系列，就來下載 AMD x86_64 : r1000-gcc1220_glibc236_x86_64-GPL.txz。基於 DS723+ 有 Docker 可用，這次就全在 Docker 內運行，直接叫一個 Ubuntu 22.04 出來使用：

# apt update -y ; apt upgrade -y ; install sudo vim openssh-server -y ; service ssh restart;

後續遠端進去後，就可以輕鬆建置完畢，最後實測 7.2 toolchain 編譯出來的 tmux 的確就可以正常運行啦。其餘編譯細節就參考 [Linux] cross compile tmux for Synology DS723+ via DSM 7.1 ToolChain - AMD x86 Linux 4.4.180 (r1000) 即可，僅一開始的 toolchain 換掉即可：

• global.synologydownload.com/download/ToolChain/toolchain/7.2-63134/AMD%20x86%20Linux%204.4.302%20%28r1000%29/r1000-gcc1220_glibc236_x86_64-GPL.txz
• ftp.gnu.org/pub/gnu/ncurses/ncurses-6.4.tar.gz
• github.com/libevent/libevent/releases/download/release-2.1.12-stable/libevent-2.1.12-stable.tar.gz
• github.com/tmux/tmux/releases/download/3.3a/tmux-3.3a.tar.gz