vault backup: 2025-07-22 22:14:08
Affected files: Too many files to list
This commit is contained in:
@@ -1,22 +0,0 @@
|
||||
```bash
|
||||
sudo apt update; sudo apt install -y cifs-utils lm-sensors
|
||||
```
|
||||
|
||||
1. 安裝必須的套件
|
||||
2. 修正時區
|
||||
3. `mkdir ~/log`
|
||||
4. 掛載 smb
|
||||
5. 掛載 lvm
|
||||
6. 設定 journalctl size
|
||||
7. 設定 crontab
|
||||
9. 啟動所有 docker
|
||||
10. 掛載mod [[開機自動掛載模組（modprobe nct6683）]]
|
||||
11. 設定 `sudo sensors-detect`
|
||||
|
||||
```shell
|
||||
sudo apt update; sudo apt install -y cifs-utils lm-sensors
|
||||
sudo timedatectl set-timezone Asia/Taipei
|
||||
mkdir ~/log
|
||||
|
||||
|
||||
```
|
||||
@@ -1,172 +0,0 @@
|
||||
## cut
|
||||
Linux 的 `cut` 指令是一個實用的文字處理工具，可以將每一行文字的部份字元或欄位擷取出來，以下是使用方式與範例。
|
||||
|
||||
### 擷取字元
|
||||
|
||||
對於欄位寬度是固定的資料，可以使用擷取固定位置字元的方式，把指定的欄位抓出來，典型的例子就是從 `ls` 指令的輸出中擷取檔案權限。假設我們的 `ls` 指令與輸出資料如下：
|
||||
```bash
|
||||
# 僅輸出最後 5 筆檔案資訊
|
||||
ls -l | tail -n 5
|
||||
```
|
||||
|
||||
```
|
||||
drwxr-xr-x 2 gtwang gtwang 4096 11月 7 22:29 影片
|
||||
drwxr-xr-x 7 gtwang gtwang 4096 2月 6 21:01 文件
|
||||
drwxr-xr-x 4 gtwang gtwang 4096 2月 22 21:09 桌面
|
||||
drwxr-xr-x 2 gtwang gtwang 4096 1月 6 2017 模板
|
||||
drwxrwxr-x 2 gtwang gtwang 4096 1月 6 2017 音樂
|
||||
```
|
||||
|
||||
如果我們想要擷取第一欄中的檔案權限（也就是第 2 個字元到第 10 個字元），可以使用 `cut` 指令配合 `-c` 參數，將每一行的第 2 個字元至第 10 個字元抓出來：
|
||||
|
||||
```bash
|
||||
# 擷取第 2 個字元至第 10 個字元
|
||||
ls -l | tail -n 5 | cut -c 2-10
|
||||
```
|
||||
|
||||
Output:
|
||||
```
|
||||
rwxr-xr-x
|
||||
rwxr-xr-x
|
||||
rwxr-xr-x
|
||||
rwxr-xr-x
|
||||
rwxrwxr-x
|
||||
```
|
||||
|
||||
如果要擷取多個不連續的的區段，逗號分隔每個區段，例如：
|
||||
|
||||
```bash
|
||||
# 擷取第 2-3 個、第 5-6 個與第 8-9 個字元
|
||||
ls -l | tail -n 5 | cut -c 2-3,5-6,8-9
|
||||
```
|
||||
|
||||
Output:
|
||||
```
|
||||
rwr-r-
|
||||
rwr-r-
|
||||
rwr-r-
|
||||
rwr-r-
|
||||
rwrwr-
|
||||
```
|
||||
|
||||
### 排除字元
|
||||
|
||||
上面的範例中我們都是設定要擷取的部份，如果想要設定排除的部份，可以加上 `--complement` 這個補集參數，這樣 `cut` 就會將指定的部份刪除，留下剩餘的部份：
|
||||
|
||||
```bash
|
||||
# 排除第 2 個字元至第 10 個字元
|
||||
ls -l | tail -n 5 | cut -c 2-10 --complement
|
||||
```
|
||||
|
||||
Output:
|
||||
```
|
||||
d 2 gtwang gtwang 4096 11月 7 22:29 影片
|
||||
d 7 gtwang gtwang 4096 2月 6 21:01 文件
|
||||
d 4 gtwang gtwang 4096 2月 22 21:09 桌面
|
||||
d 2 gtwang gtwang 4096 1月 6 2017 模板
|
||||
d 2 gtwang gtwang 4096 1月 6 2017 音樂
|
||||
```
|
||||
|
||||
### 擷取欄位
|
||||
|
||||
若我們的資料欄位寬度不是固定的，而是使用特定的字元分隔不同的欄位，例如逗點分隔檔（csv 檔）：
|
||||
```
|
||||
5.1,3.5,1.4,0.2,"setosa"
|
||||
4.9,3,1.4,0.2,"setosa"
|
||||
7,3.2,4.7,1.4,"versicolor"
|
||||
6.4,3.2,4.5,1.5,"versicolor"
|
||||
5.9,3,5.1,1.8,"virginica"
|
||||
```
|
||||
|
||||
若要擷取這個 csv 檔的特定欄位，可以使用 `cut` 指令加上 `-d` 參數指定欄位分隔字元，並以 `-f` 參數指定欲擷取的欄位，例如擷取出第 2 個欄位：
|
||||
|
||||
```bash
|
||||
# 擷取 CSV 檔的第二個欄位
|
||||
cut -d , -f 2 data.csv
|
||||
```
|
||||
|
||||
Output:
|
||||
```
|
||||
3.5
|
||||
3
|
||||
3.2
|
||||
3.2
|
||||
3
|
||||
```
|
||||
|
||||
若要擷取多個欄位，也是使用逗號分隔每個欄位：
|
||||
|
||||
```bash
|
||||
# 擷取 CSV 檔的第 1-3 個與第 5 個欄位
|
||||
cut -d , -f 1-3,5 data.csv
|
||||
```
|
||||
|
||||
```
|
||||
5.1,3.5,1.4,"setosa"
|
||||
4.9,3,1.4,"setosa"
|
||||
7,3.2,4.7,"versicolor"
|
||||
6.4,3.2,4.5,"versicolor"
|
||||
5.9,3,5.1,"virginica"
|
||||
```
|
||||
|
||||
Linux 中的 `/etc/passwd` 檔案內容是以冒號分隔欄位的，若要從中擷取特定的欄位，可以指定以冒號為分隔字元：
|
||||
|
||||
```bash
|
||||
# 擷取 /etc/passwd 的第 1 個與第 7 個欄位
|
||||
head -n 5 /etc/passwd | cut -d : -f 1,7
|
||||
```
|
||||
|
||||
```
|
||||
root:/bin/bash
|
||||
daemon:/usr/sbin/nologin
|
||||
bin:/usr/sbin/nologin
|
||||
sys:/usr/sbin/nologin
|
||||
sync:/bin/sync
|
||||
```
|
||||
|
||||
### 排除欄位
|
||||
|
||||
若要排除某些特定欄位，而留下其餘的欄位，同樣可以使用 `--complement` 參數：
|
||||
|
||||
```bash
|
||||
# 排除 CSV 檔的第二個欄位
|
||||
cut -d , -f 2 --complement data.csv
|
||||
```
|
||||
|
||||
```
|
||||
5.1,1.4,0.2,"setosa"
|
||||
4.9,1.4,0.2,"setosa"
|
||||
7,4.7,1.4,"versicolor"
|
||||
6.4,4.5,1.5,"versicolor"
|
||||
5.9,5.1,1.8,"virginica"
|
||||
```
|
||||
|
||||
### 輸出分隔字元
|
||||
`cut` 在輸出多欄位的資料時，預設會以輸入檔案所使用的分隔字元來分隔輸出的欄位，若要改變輸出欄位的分隔字元，可以使用 `--output-delimiter` 參數來指定：
|
||||
|
||||
```bash
|
||||
# 指定輸出欄位分隔字元
|
||||
head -n 5 /etc/passwd | cut -d : -f 1,7 --output-delimiter="^_^"
|
||||
```
|
||||
|
||||
```
|
||||
root^_^/bin/bash
|
||||
daemon^_^/usr/sbin/nologin
|
||||
bin^_^/usr/sbin/nologin
|
||||
sys^_^/usr/sbin/nologin
|
||||
sync^_^/bin/sync
|
||||
```
|
||||
|
||||
### 實用範例
|
||||
Linux 的系統管理者時常會需要使用 `ps` 指令查看各行程的狀態，但由於 `ps` 的輸出資訊很多，如果我們只想看程式的 PID 與指令內容，就可以用 `cut` 把要用的資訊擷取來：
|
||||
|
||||
```bash
|
||||
# 找出所有 Python 程式的 PID 與指令內容
|
||||
ps aux | grep python | sed 's/\s\+/ /g' | cut -d ' ' -f 2,11-
|
||||
```
|
||||
|
||||
```
|
||||
17100 grep --color=auto python
|
||||
27904 /usr/bin/python -Es /usr/sbin/tuned -l -P
|
||||
33890 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
|
||||
```
|
||||
@@ -1,57 +0,0 @@
|
||||
`scp` 指令的語法跟一般的 `cp` 類似，只不過 `scp` 可以在不同的 Linux 主機之間複製檔案，其語法為：
|
||||
```
|
||||
scp [帳號@來源主機]:來源檔案 [帳號@目的主機]:目的檔案
|
||||
```
|
||||
|
||||
# 保留檔案時間與權限
|
||||
若要讓檔案在複製之後，還可保留原本的修改時間、存取時間與權限，可以加上 `-p` 參數：
|
||||
```
|
||||
scp -p /path/file1 myuser@192.168.0.1:/path/file2
|
||||
```
|
||||
|
||||
# 資料壓縮
|
||||
若要將資料壓縮之後再傳送，減少網路頻寬的使用量，可以加上 `-C` 參數：
|
||||
```
|
||||
scp -C /path/file1 myuser@192.168.0.1:/path/file2
|
||||
```
|
||||
|
||||
# 限制傳輸速度
|
||||
若要限制網路的使用頻寬，可以用 `-l` 指定可用的網路頻寬上限值（單位為 Kbit/s）：
|
||||
```
|
||||
# 限制傳輸速度為 400 Kbit/s
|
||||
scp -l 400 /path/file1 myuser@192.168.0.1:/path/file2
|
||||
```
|
||||
|
||||
這樣就會限制 `scp` 只能使用 `400` Kbit/s，也就是 `400 / 8 = 50` KB/s。
|
||||
|
||||
# 自訂連接埠
|
||||
一般 SSH 伺服器的連接埠號為 22，如果遇到使用非標準埠號的伺服器，可以用 `-P` 來指定埠號。若遠端的 SSH 伺服器使用 `2222` 這個連接埠，我們就可以這樣複製檔案：
|
||||
```
|
||||
# 使用 2222 連接埠
|
||||
scp -P 2222 /path/file1 myuser@192.168.0.1:/path/file2
|
||||
```
|
||||
|
||||
# IPv4 與 IPv6
|
||||
`-4` 與 `-6` 兩個參數分別可以讓 `scp` 使用 IPv4 與 IPv6 來傳輸資料：
|
||||
```
|
||||
# 使用 IPv4
|
||||
scp -4 /path/file1 myuser@192.168.0.1:/path/file2
|
||||
|
||||
# 使用 IPv6
|
||||
scp -6 /path/file1 myuser@192.168.0.1:/path/file2
|
||||
```
|
||||
|
||||
# 更快的方法：使用SSH+TAR
|
||||
```
|
||||
ssh 使用者@主機 "cd 目標目錄 ;tar -zcvf - 目標" | cat > 目標.tar.gz
|
||||
```
|
||||
|
||||
例：
|
||||
```
|
||||
ssh 192.168.0.22 "cd /var ;tar -zcvf - log" | cat > 22_log.tar.gz
|
||||
```
|
||||
|
||||
# 參考
|
||||
- [SSH + TAR 取代 SCP @ Vexed's Blog :: 隨意窩 Xuite日誌](https://blog.xuite.net/vexed/tech/586811949)
|
||||
- [Linux中互传文件：ssh+tar 与Scp 比较 - 简书](https://www.jianshu.com/p/856a2dc883e0)
|
||||
- [轉貼--ssh tar 命令把遠端檔拉回來或推過去 --- 山城風雲的點滴](http://jimsung168.blogspot.com/2014/01/ssh-tar.html)
|
||||
@@ -1,4 +0,0 @@
|
||||
## 列出系統中的 systemd service
|
||||
```bash
|
||||
systemctl list-units --type=service
|
||||
```
|
||||
@@ -1,14 +0,0 @@
|
||||
用`timedatectl`可以看現在的時間、時區等等。也可以改變時區。
|
||||
![[Pasted image 20220516125616.png]]
|
||||
|
||||
用`timedatectl list-timezones`列出所有時區，我們已經知道我們的時區是Taipei，所以可以用grep直接把它抓出來：
|
||||
```bash
|
||||
timedatectl list-timezones | grep -i taipei
|
||||
```
|
||||
結果如下：
|
||||
![[Pasted image 20220516125742.png]]
|
||||
|
||||
設定時區：
|
||||
```
|
||||
timedatectl set-timezone Asia/Taipei
|
||||
```
|
||||
@@ -1,42 +0,0 @@
|
||||
# 安裝
|
||||
根據[# Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/)來安裝Docker engine。
|
||||
|
||||
# 指令
|
||||
## 列出可用的版本
|
||||
```bash
|
||||
# List the available versions:
|
||||
apt-cache madison docker-ce | awk '{ print $3 }'
|
||||
|
||||
5:24.0.0-1~debian.11~bullseye
|
||||
5:23.0.6-1~debian.11~bullseye
|
||||
...
|
||||
```
|
||||
|
||||
## 列出 container
|
||||
`docker ps`會列出執行中的container（但是停止的不會）
|
||||
```bash
|
||||
sudo docker ps
|
||||
```
|
||||
|
||||
如果也要列出已停止的container
|
||||
```bash
|
||||
sudo docker ps -a
|
||||
```
|
||||
|
||||
## 刪除 container
|
||||
Container必須是停止狀態才可以刪除
|
||||
```bash
|
||||
sudo docker rm <CONTAINER_ID>
|
||||
```
|
||||
|
||||
## 進入 container 執行 bash
|
||||
```bash
|
||||
docker run -i -t <CONTAINER_NAME> /bin/bash
|
||||
```
|
||||
|
||||
## 列出 image
|
||||
```bash
|
||||
sudo docker image ls
|
||||
or
|
||||
sudo docker images
|
||||
```
|
||||
@@ -1,37 +0,0 @@
|
||||
---
|
||||
tags:
|
||||
aliases:
|
||||
date: 2025-01-07
|
||||
time: 22:52:59
|
||||
description:
|
||||
---
|
||||
|
||||
在啟用 NAS 的 UPS server 之後，可以安裝 `nut-client` 來接收 NAS 的通知以進行關機。
|
||||
|
||||
## 安裝套件
|
||||
```bash
|
||||
sudo apt install nut-client
|
||||
```
|
||||
|
||||
## 測試
|
||||
```bash
|
||||
upsc ups@192.168.1.11
|
||||
```
|
||||
|
||||
## 設定
|
||||
```bash
|
||||
sudo vim /etc/nut/upsmon.conf
|
||||
```
|
||||
|
||||
加入 `MODE=netclient`
|
||||
|
||||
```bash
|
||||
sudo vim /etc/nut/upsmon.conf
|
||||
```
|
||||
|
||||
加入 `MONITOR ups@192.168.1.11 1 monuser secret slave`
|
||||
|
||||
# 參考來源
|
||||
- [Linux 下使用 NUT 实现断电自动关机 | varkai](https://varkai.com/posts/operation/linux-uses-nut-to-realize-automatic-poweroff/)
|
||||
- [ups - Use Synology as NUT server for Ubuntu Server 20.04 - Ask Ubuntu](https://askubuntu.com/questions/1244064/use-synology-as-nut-server-for-ubuntu-server-20-04)
|
||||
- [UPS 低电压时通过群晖实现 Ubuntu 自动关机 - 杜老师说](https://dusays.com/557/)
|
||||
@@ -1,109 +0,0 @@
|
||||
## 安裝 Watchtower
|
||||
```shell
|
||||
docker pull Watchtower
|
||||
```
|
||||
|
||||
## 使用方法
|
||||
```shell
|
||||
docker run --detach \
|
||||
--name watchtower \
|
||||
--volume /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower
|
||||
```
|
||||
|
||||
使用剛剛的方法會拉取最新鏡像，但並不會自動刪除舊有鏡像，時間一長就會佔用很大空間，這裡可以使用 `--cleanup` 選項，在更新完舊容器之後自動刪除舊鏡像
|
||||
|
||||
```shell
|
||||
docker run -d \
|
||||
--name watchtower \
|
||||
--restart always \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower \
|
||||
--cleanup
|
||||
```
|
||||
|
||||
### 或使用 docke-compose.yml
|
||||
```yaml
|
||||
version: "3"
|
||||
services:
|
||||
watchtower:
|
||||
image: containrrr/watchtower
|
||||
restart: always
|
||||
volumes:
|
||||
- /var/run/docker.sock:/var/run/docker.sock
|
||||
command: --interval 86400 --cleanup
|
||||
```
|
||||
|
||||
### 設置自動更新檢測頻率
|
||||
Watchtower 默認是每 5min 檢測一次，如果需要更改週期，可以使用 `--interval`、`-i` 選項
|
||||
如設定每小時檢測一次：
|
||||
```shell
|
||||
docker run -d \
|
||||
--name watchtower \
|
||||
--restart always \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower \
|
||||
--cleanup \
|
||||
-i 3600
|
||||
```
|
||||
|
||||
`-i 3600`：這裡的 `3600` 是設置的時間週期，單位是**秒** ， `3600` 即 1 小時
|
||||
|
||||
### 指定更新檢測時間
|
||||
除了設置頻率，還可以使用 `--schedule`、`-s` 選項指定時間 如指定每天 UTC+8 時間凌晨 3 點更新。
|
||||
```shell
|
||||
docker run -d \
|
||||
--name watchtower \
|
||||
--restart always \
|
||||
-e TZ=Asia/Taipei \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower \
|
||||
--cleanup \
|
||||
-s "0 0 3 * * *"
|
||||
```
|
||||
|
||||
這裡的執行時間為 UTC 時間，如果不指定時區，會比台北的 UTC+8:00 時間晚 8 小時
|
||||
|
||||
### 制定需要更新的容器
|
||||
如果不想更新所有容器，可以設置指定的容器進行更新
|
||||
以 `nginx` 和 `netdata` 這兩個容器舉例：
|
||||
```shell
|
||||
docker run -d \
|
||||
--name watchtower \
|
||||
--restart always \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower \
|
||||
--cleanup \
|
||||
nginx netdata
|
||||
```
|
||||
|
||||
這裡指定的容器只需要填寫**容器名**，而不是填寫該容器的**鏡像名**
|
||||
|
||||
## 手動更新
|
||||
如果不想在使用容器時被自動更新打斷，可以使用 Watchtower 進行手動更新
|
||||
由於是手動更新，Watchtower 只需要用到一次，可以添加 `--rm` 和 `--run-once` 參數，在更新完之後過河拆橋
|
||||
|
||||
### 手動更新所有容器
|
||||
```shell
|
||||
docker run --rm \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower \
|
||||
--cleanup \
|
||||
--run-once
|
||||
```
|
||||
|
||||
## 手動更新指定容器
|
||||
繼續以 `nginx` 和 `netdata` 這兩個容器舉例
|
||||
|
||||
```shell
|
||||
docker run --rm \
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
containrrr/watchtower \
|
||||
--cleanup \
|
||||
--run-once \
|
||||
nginx netdata
|
||||
```
|
||||
|
||||
## 參考
|
||||
- [使用Watchtower自動更新Docker鏡像和容器 - Docker容器 - 計算機 | 🧂 = 鹽🧂的記事本 = ( ´∀｀)ヵヵヵ](https://www.sio.moe/2021/12/18/computer/Docker-Container/Use-Watchtower-to-automatically-update-Docker-images-and-containers/)
|
||||
- [storjlabs/watchtower Tags | Docker Hub](https://hub.docker.com/r/storjlabs/watchtower/tags)
|
||||
@@ -1,29 +0,0 @@
|
||||
{
|
||||
"nodes":[
|
||||
{"id":"2387a7bafd0d1fa1","type":"text","text":"Linux","x":-60,"y":-60,"width":112,"height":60,"color":"1"},
|
||||
{"id":"480671b59b65fbee","type":"text","text":"網路","x":-260,"y":-200,"width":123,"height":60},
|
||||
{"id":"0da49f9f13cb5ea0","type":"text","text":"虛擬化","x":140,"y":-200,"width":125,"height":60},
|
||||
{"id":"67febece2a817d3a","type":"text","text":"系統管理","x":140,"y":80,"width":125,"height":60},
|
||||
{"id":"c30ec48841c09729","type":"text","text":"# LOG 管理\n[[journalctl]]","x":341,"y":80,"width":186,"height":100},
|
||||
{"id":"89e25cea38eee1c6","type":"text","text":"# 定時操作\n[[crontab]]","x":347,"y":220,"width":180,"height":100},
|
||||
{"id":"0211a8b636cb3542","type":"text","text":"指令操作","x":-262,"y":80,"width":125,"height":60},
|
||||
{"id":"584c8fe580aa5c65","type":"text","text":"- [[cut]]\n- [[scp]]\n- [[timedatectl]]\n- [[systemd]]","x":-620,"y":55,"width":250,"height":110},
|
||||
{"id":"5396ff224cf2433d","type":"text","text":"- [[Apache]]\n- [[Gitea]]\n- [[Grafana]]\n- [[Nextcloud]]\n- [[Pelican blog]]\n- [[Proxmox VE]]\n- [[Storj]]\n- [[filebrowser]]\n- [[freshrss]]\n- [[Grafana]]","x":-700,"y":-577,"width":242,"height":277},
|
||||
{"id":"631ba79f09378fa8","type":"text","text":"![[Docker|Docker]]","x":312,"y":-299,"width":348,"height":219},
|
||||
{"id":"d5901d4a7879a984","type":"text","text":"架站","x":-432,"y":-468,"width":125,"height":60},
|
||||
{"id":"8b9a102062abf2ea","type":"text","text":"![[smb client]]","x":-699,"y":-231,"width":330,"height":201}
|
||||
],
|
||||
"edges":[
|
||||
{"id":"2621855f17f1fce7","fromNode":"2387a7bafd0d1fa1","fromSide":"right","toNode":"0da49f9f13cb5ea0","toSide":"left"},
|
||||
{"id":"63fe0dc1ef02bcf0","fromNode":"2387a7bafd0d1fa1","fromSide":"right","toNode":"67febece2a817d3a","toSide":"left"},
|
||||
{"id":"8b1293fe476ce994","fromNode":"2387a7bafd0d1fa1","fromSide":"left","toNode":"480671b59b65fbee","toSide":"right"},
|
||||
{"id":"7b14c2274a6a7dce","fromNode":"480671b59b65fbee","fromSide":"left","toNode":"8b9a102062abf2ea","toSide":"right"},
|
||||
{"id":"3fb7bd17056728f2","fromNode":"0da49f9f13cb5ea0","fromSide":"right","toNode":"631ba79f09378fa8","toSide":"left"},
|
||||
{"id":"47dcc8ff2aa219d2","fromNode":"67febece2a817d3a","fromSide":"right","toNode":"c30ec48841c09729","toSide":"left"},
|
||||
{"id":"b9cbf23293526def","fromNode":"67febece2a817d3a","fromSide":"right","toNode":"89e25cea38eee1c6","toSide":"left"},
|
||||
{"id":"305a94a3648fc58b","fromNode":"d5901d4a7879a984","fromSide":"left","toNode":"5396ff224cf2433d","toSide":"right"},
|
||||
{"id":"1007d8512d956cdb","fromNode":"480671b59b65fbee","fromSide":"left","toNode":"d5901d4a7879a984","toSide":"right"},
|
||||
{"id":"c6875871d1de0864","fromNode":"2387a7bafd0d1fa1","fromSide":"left","toNode":"0211a8b636cb3542","toSide":"right"},
|
||||
{"id":"40f0ca450747f830","fromNode":"0211a8b636cb3542","fromSide":"left","toNode":"584c8fe580aa5c65","toSide":"right"}
|
||||
]
|
||||
}
|
||||
@@ -1,84 +0,0 @@
|
||||
### 加入
|
||||
使用`crontab -e`，然後加入這一行：
|
||||
`*/1 * * * * /home/awin/script/ddns.sh`
|
||||
|
||||
### 說明
|
||||
![[Pasted image 20240111231507.png]]
|
||||
依序是 **分鐘, 小時, 日期, 月份, 星期, command**
|
||||
參數為 0-59, 0-23, 1-31, 1-21, 0-6, 需要執行的command
|
||||
**※ 星期參數為 0 代表星期日**
|
||||
|
||||
- 【*】：星號，代表任何時刻都接受的意思
|
||||
- 【,】：逗號，代表分隔時段。例如：30 9,17 * * * command，代表早上 9 點半和下午五點半都執行 command。
|
||||
- 【-】：減號，代表一段時間範圍。例如：15 9-12 * * * command，代表從 9 點到 12 點的每個 15 分都執行 command。
|
||||
- 【/n】：斜線，n 代表數字，表示每個 n 單位間隔。例如：*/5 * * * * command，代表每隔 5 分鐘執行一次 command。
|
||||
|
||||
還有一些人性化的參數，一次取代全部五個數字參數
|
||||
- 【@reboot】 ：僅在開機的時候執行一次。
|
||||
- 【@yearly】 ：一年執行一次，和0 0 1 1 * command效果一樣。
|
||||
- 【@annually】：（和@yearly一樣）
|
||||
- 【@monthly】：一個月執行一次，和0 0 1 * * command效果一樣。
|
||||
- 【@weekly】：一個星期執行一次，和0 0 * * 0 command效果一樣。
|
||||
- 【@daily】：每天執行，和0 0 * * * command效果一樣。
|
||||
- 【@midnight】：（和@daily一樣）
|
||||
- 【@hourly】 ：每小時執行，和0 * * * * command效果一樣。
|
||||
|
||||
### 範例
|
||||
- 每 5 分鐘執行一次：
|
||||
- `*/5 * * * * root /usr/libexec/atrun`
|
||||
- 每 5 小時執行一次
|
||||
- `* */5 * * * root /usr/libexec/atrun`
|
||||
- 每天 AM 5:00 執行指令(星號與星號之間要有空隔)
|
||||
- `00 05 * * * username /bin/bash /路徑/command`
|
||||
- 1 至 20 號每天執行一次
|
||||
- `0 1 1-20 * * root /usr/libexec/atrun`
|
||||
- 當分針移到第 5 分時，執行此 cron
|
||||
- `5 * * * * root /usr/libexec/atrun`
|
||||
- 當時針移到 1 點 1 分時，執行此 cron
|
||||
- `1 1 * * * root /usr/libexec/atrun`
|
||||
- 每週一的 1 點 1 分，執行
|
||||
- `1 1 * * 1 root /usr/libexec/atrun`
|
||||
- 2 月 29 日時針到 1 點 1 分，執行
|
||||
- `1 1 29 2 * root /usr/libexec/atrun`
|
||||
- 8 點到 16 點每 5 分鐘執行一次 cron
|
||||
- `/5 8-16 * * * root /usr/libexec/atrun`
|
||||
|
||||
### crontab 命令
|
||||
#### 啟動
|
||||
`sudo service cron start`
|
||||
|
||||
#### 重新啟動
|
||||
`/etc/init.d/cron restart`
|
||||
|
||||
#### 查詢service狀態
|
||||
`sudo /etc/init.d/cron status`
|
||||
|
||||
#### 編輯 crontab
|
||||
`crontab -e`
|
||||
|
||||
### `awin` 的 crontab
|
||||
```
|
||||
# m h day mon weekday command
|
||||
*/5 * * * * /home/awin/script/clean_nextcloud.sh
|
||||
```
|
||||
|
||||
### `root` 的 crontab
|
||||
```
|
||||
# m h day mon dow command
|
||||
*/3 * * * * /home/awin/script/ddns.sh > /home/awin/log/ddns.log 2>&1
|
||||
*/5 * * * * /home/awin/script/clean_nextcloud.sh > /home/awin/log/clean_nextcloud.log 2>&1
|
||||
1 2 * * 1 /home/awin/script/backup_adguardhome.sh > /home/awin/log/backup_docker_adguardhome.log 2>&1
|
||||
2 2 * * 1 /home/awin/script/backup_filebrowser.sh > /home/awin/log/backup_docker_filebrowser.log 2>&1
|
||||
3 2 * * 1 /home/awin/script/backup_freshrss.sh > /home/awin/log/backup_docker_freshrss.log 2>&1
|
||||
4 2 * * 1 /home/awin/script/backup_gitea.sh > /home/awin/log/backup_docker_gitea.log 2>&1
|
||||
5 2 * * 1 /home/awin/script/backup_immich.sh > /home/awin/log/backup_docker_immich.log 2>&1
|
||||
1 2 * * 2 /home/awin/script/backup_nextcloud.sh > /home/awin/log/backup_docker_nextcloud.log 2>&1
|
||||
* * 1 * * /home/awin/script/backup_dotfiles_awin-pc2.sh > /home/awin/log/backup_dotfiles_awin-pc2.log 2>&1
|
||||
1 1 * * * /home/awin/script/rsync_nasphoto.sh > /home/awin/log/rsync_nasphoto.log 2>&1
|
||||
@reboot /home/awin/script/reboot_echo.sh > /home/awin/log/reboot.log 2>&1
|
||||
|
||||
## Restart Docker containers
|
||||
# m h day mon dow command
|
||||
0 4 * * * docker restart grafana-prometheus-local_data_exporter-1 > /home/awin/log/restart_grafana-prometheus-local_data_exporter-1.log 2>&1
|
||||
```
|
||||
|
||||
@@ -1,38 +0,0 @@
|
||||
# 看磁碟UUID
|
||||
```bash
|
||||
sudo blkid
|
||||
```
|
||||
```result
|
||||
/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="62C9-51DB" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="bd53c125-01"
|
||||
/dev/mmcblk0p2: LABEL="rootfs" UUID="2b2cb0b0-aa00-4bd0-b775-4abc1ff31eb2" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="bd53c125-02"
|
||||
/dev/sda1: UUID="8bd933c6-2625-498f-84cf-0b1394aa3f5e" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="6e7fd2d9-1c28-4570-aae2-022f5345781f"
|
||||
```
|
||||
|
||||
其中，`UUID="XXXXXXX....."` 這一串就是硬碟的UUID，複製下來，等一下要填到 `fstab` 裡面。
|
||||
|
||||
# `/etc/fstab`
|
||||
打開 `/etc/fstab`，加入一行：
|
||||
```config
|
||||
UUID=8bd933c6-2625-498f-84cf-0b1394aa3f5e /extusb1/storj ext4 defaults,nofail 0 0
|
||||
```
|
||||
|
||||
- `UUID=8bd933c6-2625-498f-84cf-0b1394aa3f5e`：指定要掛載的磁區是那一個
|
||||
- `/extusb1/storj`：指定要掛載的目錄
|
||||
- `ext4`: 指定要掛載的格式
|
||||
- `defaults,nofail`：檔案格式參數區。`nofail` 是說要是掛載失敗不要產生錯誤訊息，避免因為硬碟壞掉而卡在開機畫面，造成開不了機。尤其是當你的電腦沒有螢幕、鍵盤的時候，會很麻煩。
|
||||
- `0`：是否可以被 dump 指令備份 (0：不要做備份﹔1：要做備份﹔2：要做備份，重要度比 1 小)。
|
||||
- `0`：是否於開機時以 fsck 檢驗磁區 (0：不檢驗﹔1：先檢驗﹔2：後檢驗)。如果是內接式的硬碟可以改成`0 1`。
|
||||
|
||||
# AWIN-PC2 的 fstab
|
||||
```
|
||||
# <file system> <mount point> <type> <options> <dump> <pass>
|
||||
/dev/disk/by-uuid/38cb80c1-504f-4b07-8a86-27e1c22b5deb / ext4 defaults 0 1
|
||||
/dev/disk/by-uuid/A2D8-2DF1 /boot/efi vfat defaults 0 1
|
||||
/swap.img none swap sw 0 0
|
||||
|
||||
UUID=be92f54f-e427-496e-83e9-a29643aa5af0 /lvm1 ext4 defaults,nofail 0 2
|
||||
//192.168.1.11/share /media/share cifs credentials=/home/awin/.smbcredentials_shareview,defaults 0 0
|
||||
//192.168.1.11/upload /media/upload cifs credentials=/home/awin/.smbcredentials_shareview,defaults 0 0
|
||||
//192.168.1.11/Backup /media/backup cifs credentials=/home/awin/.smbcredentials_backup,defaults 0 0
|
||||
//192.168.1.11/photo /media/nasphoto cifs credentials=/home/awin/.smbcredentials_photoMgr,defaults 0 0
|
||||
```
|
||||
@@ -1,14 +0,0 @@
|
||||
---
|
||||
tags:
|
||||
aliases:
|
||||
date: 2024-07-30
|
||||
time: 19:30:12
|
||||
description:
|
||||
---
|
||||
|
||||
## Allow all input
|
||||
```
|
||||
iptables -I INPUT -j ACCEPT
|
||||
```
|
||||
|
||||
# 參考來源
|
||||
@@ -1,129 +0,0 @@
|
||||
## 看log
|
||||
Raspberry Pi 4沒有`/var/log/syslog`，要使用`journalctl`。
|
||||
```bash
|
||||
journalctl
|
||||
```
|
||||
Or
|
||||
```bash
|
||||
journalctl | grep SOMETHING
|
||||
```
|
||||
|
||||
### 看系統訊息
|
||||
```bash
|
||||
journalctl -p 0
|
||||
```
|
||||
|
||||
#### Error code意思
|
||||
```
|
||||
0: 紧急情况
|
||||
1: 警报
|
||||
2: 危急
|
||||
3: 错误
|
||||
4: 警告
|
||||
5: 通知
|
||||
6: 信息
|
||||
7：调试
|
||||
```
|
||||
|
||||
### 看開機log
|
||||
```bash
|
||||
journalctl --list-boots
|
||||
```
|
||||
|
||||
- 第一個數字顯示的是journald 的唯一的啟動追蹤號碼，你可以在下一個命令中使用它來分析該特定的啟動。
|
||||
- 第二個數字是啟動ID，你也可以在指令中指定。
|
||||
- 接下來的兩個日期、時間組合是儲存在對應文件中的日誌的時間。如果你想找出某個特定日期、時間的日誌或錯誤，這就非常方便了。
|
||||
|
||||
例如：
|
||||
```bash
|
||||
journalctl -b -45
|
||||
```
|
||||
Or
|
||||
```bash
|
||||
journalctl -b 8bab42c7e82440f886a3f041a7c95b98
|
||||
```
|
||||
|
||||
也可以使用 `-x` 選項，在顯示器上加入systemd 錯誤訊息的解釋。在某些情況下，這是個救命稻草。例：
|
||||
```bash
|
||||
journalctl -xb -p 3
|
||||
```
|
||||
|
||||
### 看某一特定時間、日期的日誌記錄
|
||||
使用 `--since` 選項與 `yesterday`、`today`、`tomorrow` 或 `now` 組合。
|
||||
|
||||
以下是一些不同指令的範例。你可以根據你的需求修改它們。它們是不言自明的。以下命令中的日期、時間格式為 `"YYYY-MM-DD HH:MM:SS"`
|
||||
```bash
|
||||
journalctl --since "2020-12-04 06:00:00"
|
||||
journalctl --since "2020-12-03" --until "2020-12-05 03:00:00"
|
||||
journalctl --since yesterday
|
||||
journalctl --since 09:00 --until "1 hour ago"
|
||||
```
|
||||
|
||||
### 看內核特定的記錄
|
||||
```bash
|
||||
journalctl -k
|
||||
```
|
||||
|
||||
### 過濾出某個systemd 服務單元的特定日誌
|
||||
例如，如果要查看 NetworkManager 服務的日誌
|
||||
```bash
|
||||
journalctl -u NetworkManager.service
|
||||
```
|
||||
|
||||
如果不知道service name，看[[systemd#列出系統中的 systemd service]]
|
||||
|
||||
### 查看使用者、群組的日誌
|
||||
```bash
|
||||
id -u debugpoint # 先找出使用者的uid
|
||||
journalctl _UID=1000 --since today
|
||||
```
|
||||
|
||||
### 查看可執行檔的日誌
|
||||
```bash
|
||||
journalctl /usr/bin/gnome-shell --since today
|
||||
```
|
||||
|
||||
### 看log佔用的磁碟空間
|
||||
```bash
|
||||
journalctl --disk-usage
|
||||
```
|
||||
|
||||
### 清除日誌
|
||||
#### 手動清除
|
||||
```bash
|
||||
sudo journalctl --flush --rotate # 將所有日誌歸檔
|
||||
sudo journalctl --vacuum-time=7d # 只保留最近7天的日誌
|
||||
sudo journalctl --vacuum-time=1s # 只保留最近1秒的日誌
|
||||
```
|
||||
或者設定日誌的大小
|
||||
```bash
|
||||
sudo journalctl --vacuum-size=400M # 保留最後400M
|
||||
```
|
||||
|
||||
#### 自動清除
|
||||
修改`/etc/systemd/journald.conf`，裡面有下面幾個設定項：
|
||||
- `SystemMaxUse`: 指定日志在持久性存储中可使用的最大磁盘空间。例：`SystemMaxUse=500M`
|
||||
- `SystemKeepFree`: 指定在将日志条目添加到持久性存储时，日志应留出的空间量。例：`SystemKeepFree=100M`
|
||||
- `SystemMaxFileSize`: 控制单个日志文件在被轮换之前在持久性存储中可以增长到多大。例：`SystemMaxFileSize=100M`
|
||||
- `RuntimeMaxUse`: 指定在易失性存储中可以使用的最大磁盘空间（在 /run 文件系统内）。例：`RuntimeMaxUse=100M`
|
||||
- `RuntimeKeepFree`: 指定将数据写入易失性存储（在 /run 文件系统内）时为其他用途预留的空间数量。例：`RuntimeMaxUse=100M`
|
||||
- `RuntimeMaxFileSize`: 指定单个日志文件在被轮换之前在易失性存储（在 /run 文件系统内）所能占用的空间量。例：`RuntimeMaxFileSize=200M`
|
||||
|
||||
修改後記得重啟 `journalctl`：
|
||||
![[journalctl#重啟日誌]]
|
||||
|
||||
也請記得[[journalctl#確認日誌的完整性]]
|
||||
|
||||
### 確認日誌的完整性
|
||||
```bash
|
||||
journalctl --verify
|
||||
```
|
||||
|
||||
### 重啟日誌
|
||||
若是有改變設定，記得重啟以讓變更生效：
|
||||
```shell
|
||||
sudo systemctl restart systemd-journald
|
||||
```
|
||||
|
||||
### 參考
|
||||
- [系統運作|如何使用journalctl 檢視和分析systemd 日誌（附實例）](https://linux.cn/article-15544-1.html)
|
||||
@@ -1,42 +0,0 @@
|
||||
`lsblk -o` 可以看到所有硬碟的詳細資料，但是資料廖很大，可以在騎之後加上指定的蘭未來縮減資料量，例如：
|
||||
```bash
|
||||
sudo lsblk -o NAME,MODEL,SERIAL,WWN,HCTL
|
||||
```
|
||||
```result
|
||||
NAME MODEL SERIAL WWN HCTL
|
||||
sda ST3000VN000-1H41 W300JG66 0x5000c50069c93ec4 0:0:0:0
|
||||
└─sda1 0x5000c50069c93ec4
|
||||
├─vg1-lv1_rmeta_0
|
||||
│ └─vg1-lv1
|
||||
└─vg1-lv1_rimage_0
|
||||
└─vg1-lv1
|
||||
sdb WDC WDS480G2G0A- 20418C804426 0x5001b448bb7f096a 0:0:1:0
|
||||
├─sdb1 0x5001b448bb7f096a
|
||||
├─sdb2 0x5001b448bb7f096a
|
||||
├─sdb3 0x5001b448bb7f096a
|
||||
└─sdb4 0x5001b448bb7f096a
|
||||
sdc CT480BX500SSD1 2044E4C26B3C 0x500a0751e4c26b3c 0:0:2:0
|
||||
├─sdc1 0x500a0751e4c26b3c
|
||||
└─sdc2 0x500a0751e4c26b3c
|
||||
sdd ST1000LM035-1RK1 WDEM0VBP 0x5000c500ab7d2dde 0:0:3:0
|
||||
└─sdd1 0x5000c500ab7d2dde
|
||||
sde ST3000VN000-1H41 W300JHNF 0x5000c50069c8d4b2 0:0:4:0
|
||||
└─sde1 0x5000c50069c8d4b2
|
||||
├─vg1-lv1_rmeta_1
|
||||
│ └─vg1-lv1
|
||||
└─vg1-lv1_rimage_1
|
||||
└─vg1-lv1
|
||||
sdf TOSHIBA HDWN180 57F4K126FP9E 0x50000397cb881edb 0:0:5:0
|
||||
├─sdf1 0x50000397cb881edb
|
||||
├─sdf2 0x50000397cb881edb
|
||||
└─sdf5 0x50000397cb881edb
|
||||
└─md127
|
||||
sdg ST8000VN0022-2EL ZA19RA2H 0x5000c500a5e7e1bf 0:0:6:0
|
||||
├─sdg1 0x5000c500a5e7e1bf
|
||||
├─sdg2 0x5000c500a5e7e1bf
|
||||
└─sdg5 0x5000c500a5e7e1bf
|
||||
└─md127
|
||||
nvme0n1 ADATA LEGEND 710 2N422LABN7CR eui.324e3432324c41424ce000184e374352
|
||||
├─nvme0n1p1 eui.324e3432324c41424ce000184e374352
|
||||
└─nvme0n1p2 eui.324e3432324c41424ce000184e374352
|
||||
```
|
||||
@@ -1,187 +0,0 @@
|
||||
# PV(Physical Volume)
|
||||
|
||||
PV(Physical Volume) 就是LVM的磁碟分區。
|
||||
|
||||
## 建立PV
|
||||
建立PV的命令如下：
|
||||
```bash
|
||||
pvcreate /dev/sdb /dev/sdc /dev/sdd
|
||||
```
|
||||
|
||||
```result
|
||||
`Physical volume "/dev/sdb" successfully created`
|
||||
`Physical volume "/dev/sdc" successfully created`
|
||||
`Physical volume "/dev/sdd" successfully created`
|
||||
```
|
||||
|
||||
這樣我們就建立了3個PV。
|
||||
|
||||
## 查看 PV
|
||||
使用 `pvdisplay` 和 `pvs` 來檢視你建立的 PV。
|
||||
|
||||
`pvs` 輸出會比較簡短，例：
|
||||
```
|
||||
sudo pvs
|
||||
```
|
||||
```result
|
||||
PV VG Fmt Attr PSize PFree
|
||||
/dev/sda3 ubuntu-vg lvm2 a-- 57.62g 28.81g
|
||||
/dev/sdb1 vg1 lvm2 a-- <2.73t 0
|
||||
/dev/sdc1 vg1 lvm2 a-- <2.73t 0
|
||||
```
|
||||
|
||||
`pvdisplay` 就比較詳細：
|
||||
```
|
||||
sudo pvdisplay
|
||||
```
|
||||
```result
|
||||
--- Physical volume ---
|
||||
PV Name /dev/sdb1
|
||||
VG Name vg1
|
||||
PV Size <2.73 TiB / not usable 3.44 MiB
|
||||
Allocatable yes (but full)
|
||||
PE Size 4.00 MiB
|
||||
Total PE 715396
|
||||
Free PE 0
|
||||
Allocated PE 715396
|
||||
PV UUID cWvfBE-Vbyp-l09E-QH0O-ZZoC-AdSG-t1J7TT
|
||||
|
||||
--- Physical volume ---
|
||||
PV Name /dev/sdc1
|
||||
VG Name vg1
|
||||
PV Size <2.73 TiB / not usable 3.00 MiB
|
||||
Allocatable yes (but full)
|
||||
PE Size 4.00 MiB
|
||||
Total PE 715396
|
||||
Free PE 0
|
||||
Allocated PE 715396
|
||||
PV UUID eDdYr4-HSZC-wRBa-feGx-SHp1-Wfye-m0e1PY
|
||||
|
||||
--- Physical volume ---
|
||||
PV Name /dev/sda3
|
||||
VG Name ubuntu-vg
|
||||
PV Size 57.62 GiB / not usable 2.00 MiB
|
||||
Allocatable yes
|
||||
PE Size 4.00 MiB
|
||||
Total PE 14751
|
||||
Free PE 7376
|
||||
Allocated PE 7375
|
||||
PV UUID zUlIaB-1Uof-3eF6-z5I7-OnqJ-UYDk-gThxJQ
|
||||
```
|
||||
|
||||
# VG(Volume Group)
|
||||
|
||||
VG(Volume Group) 由 PV 組成，你可以自由的排列組合。我們拿剛剛建立的3個PV把它組成一個VG。
|
||||
|
||||
## 建立 VG
|
||||
```
|
||||
vgcreate vg1 /dev/sdb /dev/sdc /dev/sdd
|
||||
```
|
||||
|
||||
`vg1` 是你的VG 名字，可以自由更改。
|
||||
後面的`/dev/sdb`、`/dev/sdc`、`/dev/sdd` 就是你剛剛建立的 PV。
|
||||
|
||||
## 查看 VG
|
||||
使用 `vgdisplay` 和 `vgs` 來檢視你建立的 VG。
|
||||
|
||||
# LV(Logical Volume)
|
||||
|
||||
LV(Logical Volume) 可以對應到實際的硬碟，它才是可以被 mount 到 directory 的東西。LV 可以只使用 VG 某一部份的，也就是說一個VG可以切出很多LV。
|
||||
|
||||
## 建立 LV
|
||||
```
|
||||
lvcreate --size 10G --name lv1 vg1
|
||||
```
|
||||
`--size 10G` 表示 LV 的空間是 10G
|
||||
`--name lv1` 表示 LV的名字叫做 `lv1`
|
||||
最後的 `vg1` 則是你要從那一個 VG 來建立這個 LV。
|
||||
|
||||
當然可以直接指定LV使用所有的空間：
|
||||
```
|
||||
lvcreate -l +100%FREE --name lv1 vg1
|
||||
```
|
||||
`-l` 跟 `--size` 同義。
|
||||
|
||||
### 建立 raid 1
|
||||
使用 `--type raid1` 可以建立 raid 1 的 LVM，例：
|
||||
```
|
||||
lvcreate --type raid1 -l +100%FREE --name lv1 vg1
|
||||
```
|
||||
|
||||
## 查看 LV
|
||||
使用 `lvdisplay` 和 `lvs` 來檢視你建立的 LV。
|
||||
|
||||
# 格式化 LV
|
||||
建立好LV之後就可以格式化它然後掛載它，先用`lvdisplay`確認一下 LV的路徑：
|
||||
![[20240228_170525_WindowsTerminal_901x169.png]]
|
||||
格式化：
|
||||
```
|
||||
mkfs -t ext4 /dev/vg1/lv1
|
||||
```
|
||||
|
||||
# Mount LV
|
||||
|
||||
先建立一個目錄來掛載 LV:
|
||||
```
|
||||
mkdir /lvm1
|
||||
```
|
||||
|
||||
再把 LV 掛上去：
|
||||
```
|
||||
mount /dev/vg1/lv1 /lvm1
|
||||
```
|
||||
|
||||
這樣就可以在 /myLVM 操作了。
|
||||
|
||||
## 開機自動掛載
|
||||
![[開機自動掛載硬碟]]
|
||||
|
||||
# LVM 增加空間
|
||||
增加空間的大概步驟是這樣：
|
||||
1. 電腦裝上新硬碟
|
||||
2. 建立PV，如[[lvm#建立PV]]
|
||||
3. 用 `vgextend` 把這個新的 PV 加入到既有的 VG
|
||||
4. 用 `lvextend` 來擴大容量
|
||||
5. 用 `resize2fs` 來擴大容量
|
||||
|
||||
## 用 `vgextend` 新增 PV
|
||||
假設 vg1 是目前的 VG 名字，新增的 PV是 /dev/sdc：
|
||||
```
|
||||
vgextend vg1 /dev/sdc
|
||||
```
|
||||
|
||||
## 用 `lvextend` 來擴大容量
|
||||
先用`lvdisplay`確認一下 LV的路徑，假設是 `/dev/vg1/lv1`
|
||||
```
|
||||
lvextend -L +10G /dev/vg1/lv1 # 多 10G 空間
|
||||
or
|
||||
lvextend -l +40%FREE /dev/vg1/lv1 多 40% 空間
|
||||
```
|
||||
|
||||
## 用 `resize2fs` 來擴大容量
|
||||
```
|
||||
resize2fs /dev/vg1/lv1
|
||||
```
|
||||
|
||||
# LVM 換電腦
|
||||
可能你重灌，或是把硬碟從這一台電腦換到另一台電腦，這都需要重新 "active" 原本的 LVM。
|
||||
先用 `lvscan` 看看是否有找到原本的 LVM：
|
||||
![[20240311_194022_WindowsTerminal_925x99.png]]
|
||||
|
||||
如果有的話，紅框位置就是 LVM 的路徑，之後只要啟用它就可以了：
|
||||
```
|
||||
sudo lvchange -a y /dev/vg1/lv1
|
||||
```
|
||||
|
||||
之後再[[硬碟操作#掛載硬碟|mount]]它就好了。
|
||||
|
||||
# 參考
|
||||
- [What is LVM2 in Linux ?. LVM](https://medium.com/@The_CodeConductor/what-is-lvm2-in-linux-3d28b479e250)
|
||||
- [建立LVM磁區 - HackMD](https://hackmd.io/@yzai/BJUIhnAb9)
|
||||
- [LVM — pv, vg, lv](https://sean22492249.medium.com/lvm-pv-vg-lv-1777a84a3ce8)
|
||||
- [Linux LVM (建立、擴充、移除LVM磁區) 操作筆記](https://sc8log.blogspot.com/2017/03/linux-lvm-lvm.html)
|
||||
- [LVM2學習筆記](https://maxubuntu.blogspot.com/2010/05/lvm2.html)
|
||||
- [技术|如何在 Linux 中创建/配置 LVM（逻辑卷管理）](https://linux.cn/article-12670-1.html)
|
||||
- [系统运维|如何在 Linux 中扩展/增加 LVM 大小（逻辑卷调整）](https://linux.cn/article-12673-1.html)
|
||||
- [系统运维|如何在 Linux 中减少/缩小 LVM 大小（逻辑卷调整）](https://linux.cn/article-12740-1.html)
|
||||
- [使用 lvm 內建的 raid 1 功能達成硬碟故障時的高可用性](https://gholk.github.io/linux-lvm-raid-1-builtin-boot.html)
|
||||
@@ -1,292 +0,0 @@
|
||||
這裡分享我在 Ubuntu Server 22.04 用 LXC 安裝 Windows 11，以及分享內顯 i915給虛擬機的的紀錄。
|
||||
要讓虛擬機可以使用 GPU，最常見的是 GPU passthrough，但是 GPU passthrough 只能給一個虛擬機使用，要讓多個虛擬機同時使用的話，必須打開 i915 的 SR-IOV ，可以多 7 個 VGA來分享給虛擬機。
|
||||
|
||||
# 準備
|
||||
## 安裝 incus
|
||||
根據 https://linuxcontainers.org/incus/docs/main/installing/#installing 的說明，Ubuntu 22.04 還沒辦法使用 apt 來安裝，因此依照 https://github.com/zabbly/incus 的說明來安裝：
|
||||
```shell
|
||||
curl -fsSL https://pkgs.zabbly.com/key.asc | gpg --show-keys --fingerprint
|
||||
mkdir -p /etc/apt/keyrings/
|
||||
sudo curl -fsSL https://pkgs.zabbly.com/key.asc -o /etc/apt/keyrings/zabbly.asc
|
||||
|
||||
sudo sh -c 'cat <<EOF > /etc/apt/sources.list.d/zabbly-incus-stable.sources
|
||||
Enabled: yes
|
||||
Types: deb
|
||||
URIs: https://pkgs.zabbly.com/incus/stable
|
||||
Suites: $(. /etc/os-release && echo ${VERSION_CODENAME})
|
||||
Components: main
|
||||
Architectures: $(dpkg --print-architecture)
|
||||
Signed-By: /etc/apt/keyrings/zabbly.asc
|
||||
EOF'
|
||||
|
||||
sudo apt update
|
||||
sudo apt install incus
|
||||
```
|
||||
|
||||
## 設定 incus
|
||||
使用 `sudo incus admin init` 來設定，會問一堆問題，如下：
|
||||
```
|
||||
Would you like to use clustering? (yes/no) [default=no]:
|
||||
Do you want to configure a new storage pool? (yes/no) [default=yes]: no
|
||||
Would you like to create a new local network bridge? (yes/no) [default=yes]: no
|
||||
Would you like to use an existing bridge or host interface? (yes/no) [default=no]: yes
|
||||
Name of the existing bridge or host interface: enp3s0
|
||||
Would you like the server to be available over the network? (yes/no) [default=no]: yes
|
||||
Address to bind to (not including port) [default=all]:
|
||||
Port to bind to [default=8443]:
|
||||
Would you like stale cached images to be updated automatically? (yes/no) [default=yes]:
|
||||
Would you like a YAML "init" preseed to be printed? (yes/no) [default=no]:
|
||||
```
|
||||
|
||||
大部分都預設就可以。
|
||||
|
||||
## 建立 pool
|
||||
```shell
|
||||
sudo incus storage create vmpool dir source=/lvm1/lxd_storage
|
||||
```
|
||||
|
||||
## 建立 profile
|
||||
```shell
|
||||
sudo incus profile copy default windows
|
||||
```
|
||||
|
||||
編輯profile，內容如下：
|
||||
```
|
||||
config:
|
||||
limits.cpu: "16"
|
||||
limits.memory: 16GiB
|
||||
raw.qemu: -device intel-hda -device hda-duplex -audio spice
|
||||
description: 'Windows: 16CPU, 16GB RAM, 1024GB DISK'
|
||||
devices:
|
||||
eth0:
|
||||
name: eth0
|
||||
nictype: macvlan
|
||||
parent: br0
|
||||
type: nic
|
||||
root:
|
||||
path: /
|
||||
pool: vmpool
|
||||
type: disk
|
||||
vtpm:
|
||||
path: /dev/tpm0
|
||||
type: tpm
|
||||
name: windows
|
||||
used_by: []
|
||||
```
|
||||
|
||||
## 安裝需要的套件
|
||||
```shell
|
||||
sudo apt-get install genisoimage libguestfs-tools wimtools --yes
|
||||
sudo snap install distrobuilder --classic
|
||||
```
|
||||
|
||||
## 轉換 ISO
|
||||
我們需要把Windows ISO轉換為lxc可用的ISO，先準備好原本的Windows ISO，這裡的檔名是 `Win11_23H2_Chinese_Traditional_x64v2.iso`，記得換成你自己的檔名。
|
||||
命令如下：
|
||||
```shell
|
||||
sudo distrobuilder repack-windows Win11_23H2_Chinese_Traditional_x64v2.iso Win11_23H2_Chinese_Traditional_x64v2.lxd.iso
|
||||
```
|
||||
|
||||
我們把 `Win11_23H2_Chinese_Traditional_x64v2.iso` 轉為 `Win11_23H2_Chinese_Traditional_x64v2.lxd.iso`。
|
||||
|
||||
等一下 `Win11_23H2_Chinese_Traditional_x64v2.lxd.iso` 就是要餵給虛擬機安裝的檔案。
|
||||
|
||||
## 讓操作端跟 server 端可以互連
|
||||
因為 Ubuntu server 沒有 GUI，都是透過命令操作，所以當虛擬機開機之後沒有辦法顯示畫面。所以我們需要從另一台 Windows 來把虛擬機開機，並在這台 Windows 上顯示並操作安裝畫面，這樣才可以安裝 Windows 虛擬機。
|
||||
|
||||
Ubuntu server 我們就稱為 server 端。
|
||||
Windows 這邊我們就稱為操作端。
|
||||
|
||||
### server 端
|
||||
這邊我們要讓 lxc 新增一個操作端，如下：
|
||||
```shell
|
||||
sudo incus config trust add awn-pc1
|
||||
```
|
||||
然後會跳出一堆字串，類似這樣：
|
||||
```
|
||||
ucRZ8JO48d4J32MRZ1tuuvNh3Wg86Pb7LZ4QKk090BM3jA2SIRh9aDB1mQ4dZ0H76PJll1bb0YkG2ZK8l5YYPWX5Cw4UhVs2li722P5s7A45MW4B5WBXBQXFPT170L50MsMMjB8ZiVhO6Ug2JWXGwdxp897u8cELqE6AAbA901uUCBwo80qr5czfR2Pk3QS7JCRb9LFa6uKKQsQKSDHm76814UOD3Knf50E9cq3GB6C28A0B54NKBw9T5004ZQ75QqCZqBD0F32mjfAILGCI57R09RN81LHMJ0NLVAXAKQc2LTh0aHYjsO6J41ERLAQF8bk7T07cG4611YT6F57Y6lr93ZSc5L0W7F5R5RG7Xr6e0gJ6dXh5iI18uwpUrZ6MAhN6GSUSGYTqe218He5gLa3G3UMNAJY1PlLSShcV91UF3Z18QloVR8DP9O6wYa7R9LG2Cv04MDSIK8Hs94ZPQ4hsbS1BT2J5QqZ41su06R9a8WTjP9rX8hNsQz5x5744AJl2656SdUqbos4JKX9B2IbGheqK94D7Ya0SZYiODX7Y5rIWdH1P6M6e5J75nN6En0Y9UmgRCGE2WIeG6jXFhpb7
|
||||
```
|
||||
|
||||
這個記下來，等一下要在操作端輸入。
|
||||
|
||||
### 操作端
|
||||
命令：
|
||||
```
|
||||
incus remote add awin-pc2 192.168.1.24
|
||||
```
|
||||
|
||||
然後輸入剛剛那一串字串。
|
||||
|
||||
接著命令：
|
||||
```
|
||||
incus switch awin-pc2
|
||||
```
|
||||
|
||||
之後就可以在操作端啟動 server 端的虛擬機了。
|
||||
|
||||
# 建立虛擬機
|
||||
server 端命令：
|
||||
```shell
|
||||
sudo incus init --empty --vm --profile=windows $VM_NAME
|
||||
sudo incus config device add $VM_NAME install disk source=/home/awin/lxd/Win11_23H2_Chinese_Traditional_x64v2.lxd.iso boot.priority=10
|
||||
```
|
||||
|
||||
操作端命令：
|
||||
```shell
|
||||
incus start DENNY-VM-WIN11 --console=vga
|
||||
```
|
||||
|
||||
操作端會跳出一個新視窗，然後就是 Windows 的安裝流程，記得在 "Press any key to boot from CD" 文字出現的時候趕快按一個鍵進入安裝流程。
|
||||
來不及的話，左上角按鈕可以發送 `ctrl+alt+del` 來重新開機。
|
||||
|
||||
這邊要注意的是，一旦發生重開機的狀況，剛剛那個視窗會關掉，然後跳一堆錯誤訊息，像是：
|
||||
```
|
||||
(remote-viewer.exe:23816): GSpice-CRITICAL **: 22:48:14.989: _usbdk_hider_update: assertion 'priv->usbdk_api != NULL' failed
|
||||
|
||||
(remote-viewer.exe:23816): GLib-GIO-WARNING **: 22:48:15.475: Unexpectedly, UWP app `Microsoft.OutlookForWindows_1.2024.214.400_x64__8wekyb3d8bbwe' (AUMId `Microsoft.OutlookForWindows_8wekyb3d8bbwe!Microsoft.OutlookforWindows') supports 4 extensions but has no verbs
|
||||
|
||||
(remote-viewer.exe:23816): GLib-GIO-WARNING **: 22:48:15.598: Unexpectedly, UWP app `Microsoft.ScreenSketch_11.2401.37.0_x64__8wekyb3d8bbwe' (AUMId `Microsoft.ScreenSketch_8wekyb3d8bbwe!App') supports 29 extensions but has no verbs
|
||||
|
||||
(remote-viewer.exe:23816): GLib-GIO-WARNING **: 22:48:15.600: Unexpectedly, UWP app `Clipchamp.Clipchamp_3.0.10220.0_neutral__yxz26nhyzhsrt' (AUMId `Clipchamp.Clipchamp_yxz26nhyzhsrt!App') supports 41 extensions but has no verbs
|
||||
|
||||
(remote-viewer.exe:23816): GSpice-CRITICAL **: 22:48:15.677: _usbdk_hider_update: assertion 'priv->usbdk_api != NULL' failed
|
||||
|
||||
(remote-viewer.exe:23816): GSpice-WARNING **: 22:48:15.677: Warning no automount-inhibiting implementation available
|
||||
Error: tls: failed to send closeNotify alert (but connection was closed anyway): write tcp 192.168.1.24:8443->192.168.1.154:50714: write: broken pipe
|
||||
```
|
||||
|
||||
這時用 `incus console $VM_NAME --type=vga` 就可以再次連上已開機的虛擬機，不要用 `incus start DENNY-VM-WIN11 --console=vga`。
|
||||
只要虛擬機沒有關機，就是用 `incus console $VM_NAME --type=vga` 來連上畫面。
|
||||
關機的情況下才是用 `incus start DENNY-VM-WIN11 --console=vga` 來開機並顯示畫面。
|
||||
|
||||
再來 Windows 11 沒有網路會無法安裝，所以要跳過網路檢查，在最早的安裝畫面按 `shift+F10` 打開 command line，然後輸入：
|
||||
```
|
||||
oobe/bypassnro
|
||||
```
|
||||
|
||||
安裝之後，把虛擬機連上 macvlan。
|
||||
```shell
|
||||
sudo incus config device override $VM_NAME eth0 nictype=macvlan
|
||||
```
|
||||
|
||||
這樣虛擬機就有網路了。
|
||||
|
||||
## 虛擬機裝好之後
|
||||
### 虛擬機操作
|
||||
1. 把遠端桌面連線打開
|
||||
2. 下載 driver: [virtio-win-guest-tools.exe](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.248-1/virtio-win-guest-tools.exe) ，然後安裝。
|
||||
|
||||
# 分享內顯給虛擬機
|
||||
## 準備
|
||||
安裝需要的套件
|
||||
```shell
|
||||
apt install build-* dkms
|
||||
```
|
||||
|
||||
確認你的 kernel 是 6.1 ~ 6.5：
|
||||
```shell
|
||||
uname -r
|
||||
# 6.5.0-26-generic
|
||||
```
|
||||
|
||||
## 安裝 i915 Driver
|
||||
下載 i915 Driver：
|
||||
```shell
|
||||
git clone https://github.com/strongtz/i915-sriov-dkms
|
||||
```
|
||||
|
||||
進到剛剛 clone 的目錄，修改 `dkms.conf`，把 `PACKAGE_NAME` 改為 `"i915-sriov-dkms"`，把 `PACKAGE_VERSION` 改為 `"6.5"`，看你的 kernel 版號多少就改多少。我的版本是 6.5 ，所以這裡填 6.5。
|
||||
```shell
|
||||
cd i915-sriov-dkms
|
||||
nano dkms.conf
|
||||
|
||||
# 前 2 行改成這樣
|
||||
# dkms.conf
|
||||
PACKAGE_NAME="i915-sriov-dkms"
|
||||
PACKAGE_VERSION="6.5"
|
||||
```
|
||||
|
||||
安裝 driver：
|
||||
```shell
|
||||
# 記得要在 i915-sriov-dkms 這目錄裡面
|
||||
dkms add .
|
||||
dkms install -m i915-sriov-dkms -v 6.5
|
||||
dkms remove -m i915-sriov-dkms -v 6.5
|
||||
dkms install -m i915-sriov-dkms -v 6.5
|
||||
```
|
||||
|
||||
如果有出現類似以下的錯誤：
|
||||
```
|
||||
update-initramfs: Generating /boot/initrd.img-6.5.0-26-generic
|
||||
W: Possible missing firmware /lib/firmware/i915/mtl_gsc_102.0.0.1511.bin for module i915
|
||||
W: Possible missing firmware /lib/firmware/i915/mtl_huc_8.4.3_gsc.bin for module i915
|
||||
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.6.4.bin for module i915
|
||||
```
|
||||
去 [https://cgit.freedesktop.org/drm/drm-firmware/refs/](https://cgit.freedesktop.org/drm/drm-firmware/refs/) 把檔案找出來，放到 `/lib/firmware/i915/` 然後再重新安裝。
|
||||
|
||||
檢查是否有安裝成功：
|
||||
```shell
|
||||
modinfo i915 | grep vf
|
||||
|
||||
# 應該要出現如下訊息
|
||||
# parm: max_vfs:Limit number of virtual functions to allocate. (0 = no VFs [default]; N = allow up to N VFs) (uint)
|
||||
```
|
||||
|
||||
如果沒有就重新安裝試試。
|
||||
|
||||
修改 grub：
|
||||
```shell
|
||||
nano /etc/default/grub
|
||||
|
||||
# "GRUB_CMDLINE_LINUX_DEFAULT" 這一行加入："quiet intel_iommu=on i915.enable_guc=3 i915.max_vfs=7"，如下：
|
||||
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on i915.enable_guc=3 i915.max_vfs=7"
|
||||
```
|
||||
|
||||
更新 grub 和 initramfs：
|
||||
```shell
|
||||
update-initramfs -u -k all
|
||||
update-grub
|
||||
```
|
||||
|
||||
開機自動自動設定 vGPU 的數量：
|
||||
```shell
|
||||
sudo nano /etc/rc.local
|
||||
|
||||
# 加入
|
||||
echo 7 > /sys/devices/pci0000:00/0000:00:02.0/sriov_numvfs
|
||||
```
|
||||
|
||||
然後 `sudo chmod +x /etc/rc.local`
|
||||
|
||||
重開機，開機之後檢查 VGA 數量是不是有 8 個（1 個是原本的，另外 7 個是可以分享給虛擬機的 ）。
|
||||
```shell
|
||||
lspci | grep 00:02
|
||||
|
||||
# 應該找到 8 個
|
||||
00:02.0 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.1 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.2 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.3 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.4 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.5 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.6 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
00:02.7 VGA compatible controller: Intel Corporation AlderLake-S GT1 (rev 0c)
|
||||
```
|
||||
|
||||
## 設定 vGPU 給虛擬機
|
||||
可以分享的 VGA 有 `00:02.1` ~ `00:02.7` ，然後在虛擬機裡面新增一個 device：
|
||||
```shell
|
||||
sudo incus config device add $VM_NAME gpu pci address=0000:00:02.1
|
||||
```
|
||||
|
||||
然後在操作端把虛擬機開機：
|
||||
```
|
||||
incus start $VM_NAME --console=vga
|
||||
```
|
||||
|
||||
這時後會變成黑畫面，像這樣：
|
||||
![[incus_srart_display_error.png]]
|
||||
|
||||
大概等個 1~3 分鐘就會跳出開機畫面了。
|
||||
|
||||
開機好之後，裝置管理員會出現一張顯卡，去 Windows Update 更新，就會出現 Intel UHD 770 顯示卡了。
|
||||
@@ -1,43 +0,0 @@
|
||||
# Connect to SMB folder
|
||||
## 安裝
|
||||
```shell
|
||||
sudo apt-get install cifs-utils
|
||||
```
|
||||
|
||||
## 設定
|
||||
### 建立 `~/.smbcredentials` ，用來存放帳號密碼
|
||||
```shell
|
||||
touch ~/.smbcredentials
|
||||
vim ~/.smbcredentials
|
||||
```
|
||||
|
||||
依下面格式填入
|
||||
```
|
||||
username=<your_username>
|
||||
password=<your_password>
|
||||
```
|
||||
|
||||
### 讓機器每次開機就自動掛載。
|
||||
建立掛載點
|
||||
```shell
|
||||
sudo mkdir /mnt/sambashare
|
||||
```
|
||||
`/mnt/sambashare` 改成你自己喜歡的路徑
|
||||
|
||||
打開 `/etc/fstab`，填入下面這一行：
|
||||
```
|
||||
//samba_server_ip/share_name /mnt/sambashare cifs credentials=/home/pi/.smbcredentials,uid=pi,gid=pi 0 0
|
||||
```
|
||||
|
||||
檢查
|
||||
```shell
|
||||
sudo systemctl daemon-reload
|
||||
sudo mount -a
|
||||
```
|
||||
|
||||
### 範例
|
||||
```
|
||||
//192.168.1.11/share /media/share cifs credentials=/home/awin/.smbcredentials_shareview,auto 0 0
|
||||
//192.168.1.11/upload /media/upload cifs credentials=/home/awin/.smbcredentials_shareview,auto 0 0
|
||||
//192.168.1.11/Backup /media/backup cifs credentials=/home/awin/.smbcredentials_backup,auto 0 0
|
||||
```
|
||||
@@ -1,86 +0,0 @@
|
||||
# 前置條件
|
||||
|
||||
你需要有 **root** 或是 **sudo** 的權限才能更改系統的時區
|
||||
|
||||
# 檢查當前時區
|
||||
|
||||
在 Ubuntu 中，我們有三種方式查看當前時區設定
|
||||
|
||||
## 1. 使用 `timedatectl` 命令顯示當前的系統時區。
|
||||
```
|
||||
timedatectl
|
||||
```
|
||||
```result
|
||||
Local time: Fri 2021-01-07 22:45:47 UTC
|
||||
Universal time: Fri 2021-01-07 22:45:47 UTC
|
||||
RTC time: Fri 2021-01-07 22:45:48
|
||||
Time zone: Etc/UTC (UTC, +0000)
|
||||
System clock synchronized: yes
|
||||
systemd-timesyncd.service active: yes
|
||||
RTC in local TZ: no
|
||||
```
|
||||
|
||||
## 2. 查看 `/etc/localtime` 的連結指向
|
||||
```
|
||||
ls -l /etc/localtime
|
||||
```
|
||||
```result
|
||||
lrwxrwxrwx 1 root root 33 Jan 8 15:57 /etc/localtime -> ../usr/share/zoneinfo/Etc/UTC
|
||||
```
|
||||
|
||||
## 3. 查看 `/etc/timezome` 的內容
|
||||
```
|
||||
cat /etc/timezone
|
||||
```
|
||||
```result
|
||||
Etc/UTC
|
||||
```
|
||||
|
||||
# 修改時區
|
||||
|
||||
當我們檢查完時區後，接下來就是修改時區。不過假如你不知道要改的時區名稱，你可以透過以下指令來查看
|
||||
```
|
||||
timedatectl list-timezones
|
||||
```
|
||||
```result
|
||||
...
|
||||
Asia/Seoul
|
||||
Asia/Shanghai
|
||||
Asia/Singapore
|
||||
Asia/Srednekolymsk
|
||||
Asia/Taipei
|
||||
Asia/Tashkent
|
||||
Asia/Tbilisi
|
||||
Asia/Tehran
|
||||
Asia/Thimphu
|
||||
Asia/Tokyo
|
||||
...
|
||||
```
|
||||
|
||||
找到要修改的時區名稱後，接下就是以 sudo 權限執行以下命令
|
||||
```
|
||||
sudo timedatectl set-timezone 要修改的時區名稱
|
||||
```
|
||||
|
||||
例如要將系統修改為台北時區 `Asia/Taipei`，請輸入
|
||||
```
|
||||
sudo timedatectl set-timezone Asia/Taipei
|
||||
```
|
||||
|
||||
使用 `timedatectl` 指令確認時區是否正確修改
|
||||
```
|
||||
timedatectl
|
||||
```
|
||||
```result
|
||||
Local time: Fri 2021-01-08 18:38:49 CST
|
||||
Universal time: Fri 2021-01-08 10:38:49 UTC
|
||||
RTC time: Fri 2021-01-08 10:38:49
|
||||
Time zone: Asia/Taipei (CST, +0800)
|
||||
System clock synchronized: yes
|
||||
systemd-timesyncd.service active: yes
|
||||
RTC in local TZ: no
|
||||
```
|
||||
|
||||
|
||||
# 參考
|
||||
- [如何正確修改 Ubuntu 18.04 的系統時區](https://www.hanktsai.com/2021/01/configure-ubuntu1804-timezone.html)
|
||||
@@ -1,108 +0,0 @@
|
||||
## Install
|
||||
```
|
||||
sudo apt update && sudo apt install apache2
|
||||
```
|
||||
|
||||
## 測試Apache
|
||||
```
|
||||
sudo service apache2 status
|
||||
```
|
||||
|
||||
## 設置虛擬主機（Virtual Hosts）
|
||||
假設要建立2個網站*test1.ui-code.com*與*test2.ui-code.com*
|
||||
|
||||
### 建立目錄並設置權限（Permissions）
|
||||
```
|
||||
sudo mkdir -p /var/www/test1.ui-code.com/public_html
|
||||
sudo mkdir -p /var/www/test2.ui-code.com/public_html
|
||||
sudo chmod -R 755 /var/www
|
||||
```
|
||||
|
||||
### 建立測試頁面
|
||||
#### 建立test1.ui-code.com的測試頁面
|
||||
```
|
||||
sudo nano /var/www/test1.ui-code.com/public_html/index.html
|
||||
```
|
||||
填入以下內容：
|
||||
```html
|
||||
<html>
|
||||
<head>
|
||||
<title>Welcome to test1.ui-code.com</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Welcome to test1.ui-code.com</h2>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
|
||||
#### 建立test2.ui-code.com的測試頁面
|
||||
```
|
||||
sudo nano /var/www/test2.ui-code.com/public_html/index.html
|
||||
```
|
||||
填入以下內容：
|
||||
```html
|
||||
<html>
|
||||
<head>
|
||||
<title>Welcome to test2.ui-code.com</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Welcome to test2.ui-code.com</h2>
|
||||
</body>
|
||||
</html>
|
||||
```
|
||||
|
||||
### 建立虛擬主機文件（Virtual Host Files）
|
||||
虛擬主機文件位於 /etc/apache2/sites-available/ 中，其用於告訴 Apache 網頁伺服器如何響應（Respond ）各種網域請求（Request）。
|
||||
讓我們為test1.ui-code.com 網域創建一個新的虛擬主機文件。
|
||||
```
|
||||
sudo nano /etc/apache2/sites-available/test1.ui-code.com.conf
|
||||
```
|
||||
|
||||
將以下內容貼上：
|
||||
```
|
||||
<VirtualHost *:80>
|
||||
ServerAdmin webmaster@test1.ui-code.com
|
||||
ServerName test1.ui-code.com
|
||||
ServerAlias www.test1.ui-code.com
|
||||
DocumentRoot /var/www/test1.ui-code.com/public_html
|
||||
ErrorLog ${APACHE_LOG_DIR}/error.log
|
||||
CustomLog ${APACHE_LOG_DIR}/access.log combined
|
||||
</VirtualHost>
|
||||
```
|
||||
|
||||
再來為test2.ui-code.com 網域創建一個新的虛擬主機文件。
|
||||
```
|
||||
sudo nano /etc/apache2/sites-available/test2.ui-code.com.conf
|
||||
```
|
||||
|
||||
將以下內容貼上：
|
||||
```
|
||||
<VirtualHost *:80>
|
||||
ServerAdmin webmaster@test2.ui-code.com
|
||||
ServerName test2.ui-code.com
|
||||
ServerAlias www.test2.ui-code.com
|
||||
DocumentRoot /var/www/test2.ui-code.com/public_html
|
||||
ErrorLog ${APACHE_LOG_DIR}/error.log
|
||||
CustomLog ${APACHE_LOG_DIR}/access.log combined
|
||||
</VirtualHost>
|
||||
```
|
||||
|
||||
### 啟用新的虛擬主機文件（Virtual Host Files）
|
||||
現在我們有兩個虛擬主機文件，我們需要使用 a2ensite 工具來啟用它們。
|
||||
```
|
||||
sudo a2ensite test1.ui-code.com
|
||||
sudo a2ensite test2.ui-code.com
|
||||
```
|
||||
|
||||
測試配置語法是否有錯誤。
|
||||
```
|
||||
apachectl configtest
|
||||
```
|
||||
|
||||
如果「Syntax OK」，重啟 Apache。
|
||||
```
|
||||
sudo systemctl reload apache2
|
||||
```
|
||||
|
||||
## 參考
|
||||
- [[教學][Ubuntu 架站] 在 Ubuntu 20.04 安裝 Apache 網頁伺服器，並架設多個網站（多網域） | 優程式](https://ui-code.com/archives/271)
|
||||
@@ -1,30 +0,0 @@
|
||||
## docker-compose.yml
|
||||
```yaml
|
||||
version: "3"
|
||||
|
||||
networks:
|
||||
gitea:
|
||||
external: false
|
||||
|
||||
services:
|
||||
server:
|
||||
image: gitea/gitea:latest
|
||||
container_name: gitea
|
||||
environment:
|
||||
- USER_UID=1000
|
||||
- USER_GID=1000
|
||||
restart: always
|
||||
networks:
|
||||
- gitea
|
||||
volumes:
|
||||
- ./data:/data
|
||||
- /etc/timezone:/etc/timezone:ro
|
||||
- /etc/localtime:/etc/localtime:ro
|
||||
ports:
|
||||
- "8020:3000"
|
||||
- "2244:22"
|
||||
```
|
||||
|
||||
## 文件
|
||||
- [Gitea Docs: Config Cheat Sheet](https://docs.gitea.io/zh-tw/config-cheat-sheet/)
|
||||
- [How to Install Gitea on Ubuntu Using Docker](https://www.digitalocean.com/community/tutorials/how-to-install-gitea-on-ubuntu-using-docker)
|
||||
@@ -1,97 +0,0 @@
|
||||
# 要準備的檔案
|
||||
```
|
||||
├── data
|
||||
│ ├── grafana
|
||||
│ │ └── provisioning
|
||||
│ │ └── datasources
|
||||
│ │ └── datasources.yaml
|
||||
│ └── prometheus
|
||||
│ └── prometheus.yml
|
||||
├── docker-compose.yml
|
||||
```
|
||||
|
||||
- `docker-compose.yml`
|
||||
- `data/grafana/provisioning/datasources/datasources.yaml`
|
||||
- `data/prometheus/prometheus.yml`
|
||||
|
||||
# `docker-compose.yml`
|
||||
|
||||
```yaml hl:5
|
||||
services:
|
||||
grafana:
|
||||
image: grafana/grafana:latest
|
||||
restart: always
|
||||
user: "1000"
|
||||
ports:
|
||||
- "8082:3000"
|
||||
volumes:
|
||||
- ./data/grafana/data:/var/lib/grafana # data path
|
||||
- ./data/grafana/grafana.ini:/etc/grafana/grafana.ini
|
||||
- ./data/grafana/provisioning/dashboards:/etc/grafana/provisioning/dashboards
|
||||
- ./data/grafana/provisioning/datasources:/etc/grafana/provisioning/datasources
|
||||
environment:
|
||||
- GF_INSTALL_PLUGINS=grafana-clock-panel,grafana-simple-json-datasource
|
||||
|
||||
prometheus:
|
||||
image: prom/prometheus:latest
|
||||
container_name: grafana-prometheus-1
|
||||
restart: always
|
||||
command:
|
||||
- --storage.tsdb.retention.time=7d
|
||||
- --config.file=/etc/prometheus/prometheus.yml
|
||||
ports:
|
||||
- "8083:9090"
|
||||
volumes:
|
||||
- ./data/prometheus/prometheus.yml:/etc/prometheus/prometheus.yml
|
||||
|
||||
node_exporter:
|
||||
image: prom/node-exporter:latest
|
||||
restart: always
|
||||
ports:
|
||||
- "8084:9100"
|
||||
```
|
||||
|
||||
要注意 `user: "1000"` 這一行，這一行是你的 user ID，有可能會變，請用 `id -u` 確認一下。
|
||||
|
||||
# `datasources.yaml`
|
||||
|
||||
```yaml hl:6
|
||||
# datasources.yaml
|
||||
apiVersion: 1
|
||||
datasources:
|
||||
- name: Prometheus
|
||||
type: prometheus
|
||||
url: http://192.168.1.24:8083
|
||||
access: proxy
|
||||
```
|
||||
|
||||
要注意 `url: http://192.168.1.24:8083` 這一行，要更新 IP 位置。
|
||||
|
||||
# `prometheus.yml`
|
||||
|
||||
```yaml hl:11
|
||||
# prometheus.yml
|
||||
global:
|
||||
scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
|
||||
evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
|
||||
# scrape_timeout is set to the global default (10s).
|
||||
|
||||
scrape_configs:
|
||||
- job_name: 'node-exporter-local'
|
||||
scrape_interval: 5s
|
||||
static_configs:
|
||||
- targets: ['192.168.1.24:8084']
|
||||
```
|
||||
|
||||
要注意 `- targets: ['192.168.1.24:8084']` 這一行，要更新 IP 位置。
|
||||
|
||||
# Grafana template
|
||||
|
||||
template ID: `1860`
|
||||
|
||||
# 參考
|
||||
- [Docker Compose 部署监控系统 Prometheus + Grafana + Node Exporter + Cadvisor-腾讯云开发者社区-腾讯云](https://cloud.tencent.com/developer/article/2016801)
|
||||
- [基于docker-compose快速搭建Prometheus+Grafana监控系统 - 掘金](https://juejin.cn/post/7320525843737460771)
|
||||
- [Deep Dive into Using Docker Compose for Monitoring with Prometheus, Grafana, and node_exporter | by mefengl | Medium](https://medium.com/@mefengl/unknown-title-95cb5a15ce83)
|
||||
- [使用docker-compose快速部署Prometheus+grafana环境_docker-compose安装grafana-CSDN博客](https://blog.csdn.net/weixin_45070882/article/details/132104496)
|
||||
- [Dashboards | Grafana Labs](https://grafana.com/grafana/dashboards/?collector=nodeexporter&dataSource=prometheus)
|
||||
@@ -1,91 +0,0 @@
|
||||
|
||||
# 設定
|
||||
`docker-compose.yml` 如下：
|
||||
```yaml
|
||||
version: "3"
|
||||
|
||||
services:
|
||||
grafana:
|
||||
image: grafana/grafana:latest
|
||||
container_name: grafana
|
||||
restart: always
|
||||
user: "1000" # needs to be `id -u` // alternatively chown the grafana/data dir to 472:472
|
||||
ports:
|
||||
- "8081:3000" # expose for localhost
|
||||
links:
|
||||
- influxdb
|
||||
volumes:
|
||||
- ./data/grafana/data:/var/lib/grafana # data path
|
||||
- ./data/grafana/provisioning:/etc/grafana/provisioning
|
||||
- ./data/grafana/grafana.ini:/etc/grafana/grafana.ini
|
||||
environment:
|
||||
- GF_INSTALL_PLUGINS=grafana-clock-panel,grafana-simple-json-datasource
|
||||
|
||||
influxdb:
|
||||
image: influxdb
|
||||
ports:
|
||||
- "8082:8086"
|
||||
volumes:
|
||||
- ./data/influxdb/data:/var/lib/influxdb2
|
||||
|
||||
telegraf:
|
||||
image: telegraf
|
||||
user: telegraf:992 # Get 992 by `stat -c '%g' /var/run/docker.sock`, depend on system
|
||||
depends_on:
|
||||
- influxdb
|
||||
links:
|
||||
- influxdb
|
||||
volumes:
|
||||
- /var/run/docker.sock:/var/run/docker.sock:ro
|
||||
- ./data/telegraf/telegraf.conf:/etc/telegraf/telegraf.conf:ro
|
||||
environment:
|
||||
- HOST_PROC=/proc
|
||||
- HOST_SYS=/sys
|
||||
- HOST_ETC=/etc
|
||||
```
|
||||
|
||||
檔案結構如下：
|
||||
```
|
||||
data\
|
||||
grafana\
|
||||
grafana.ini
|
||||
telegraf\
|
||||
telegraf.conf
|
||||
docker-compose.yml
|
||||
```
|
||||
|
||||
`data/grafana/grafana.ini` 與 `data/telegraf/telegraf.conf` 都是需要事先準備好的檔案。
|
||||
|
||||
## 設定 InfluxDB
|
||||
|
||||
先把 docker 建立起來，然後打開 influxdb（[http://awinpi4:8082](http://awinpi4:8082/)），建立帳號、密碼、資料庫名稱。如下：
|
||||
![[20240217_212138_chrome_setup_influxdb.png]]
|
||||
|
||||
之後會出現一串Token，如下，這個要記起來。
|
||||
![[20240217_212319_chrome_1894x1254_influxdb_token.png]]
|
||||
|
||||
## 設定 telegraf
|
||||
然後打開 `./data/telegraf/telegraf.conf` ，找到 `[[outputs.influxdb_v2]]` 這個區塊，把 `urls`、`organization`、`bucket`、`token` 的值改為剛剛建立與複製的那一串。如圖：
|
||||
![[20240217_213900_Code_setup_telegraf_ini.png]]
|
||||
然後重啟 docker compose。
|
||||
|
||||
# 設定 InfluxDB 的 dashboard
|
||||
|
||||
到 [https://github.com/influxdata/community-templates#templates](https://github.com/influxdata/community-templates#templates) 挑一個 template，例如 [Raspberry Pi System Template](https://github.com/influxdata/community-templates/tree/master/raspberry-pi)，找到他的網址，如下：
|
||||
![[20240217_213108_chrome_1864x1044_raspberrypi_template_on_github.png]]
|
||||
|
||||
複製這一行，然後到 InfluxDB 的 template 去把它 import 進來。如下：
|
||||
![[20240217_213237_chrome_2753x1254_setup_influxdb.png]]
|
||||
|
||||
![[20240217_213311_chrome_2753x1254_influxdb_install_template.png]]
|
||||
|
||||
接著 Dashboards 就會出現一個 Raspberry Pi System 的 dashboard 了。
|
||||
![[20240217_213343_chrome_1624x1120_influxdb_dashboard.png]]
|
||||
|
||||
點下去之後大概是長這樣：
|
||||
![[20240217_214001_chrome_2604x1716_influxdb_dashboard.png]]
|
||||
|
||||
# 參考
|
||||
- [建構 Grafana + Influxdb v2.0 + Telegraf 監控系統(docker版) - DSA Learning](https://dsalearning.github.io/grafana/influxdb-telegraf-docker/)
|
||||
- [Raspberry Pi, InfluxDB, Grafana, Docker | by Anton Karazeev | Medium](https://medium.com/@antonkarazeev/raspberry-pi-influxdb-grafana-docker-a526575d6e6f#id_token=eyJhbGciOiJSUzI1NiIsImtpZCI6ImVkODA2ZjE4NDJiNTg4MDU0YjE4YjY2OWRkMWEwOWE0ZjM2N2FmYzQiLCJ0eXAiOiJKV1QifQ.eyJpc3MiOiJodHRwczovL2FjY291bnRzLmdvb2dsZS5jb20iLCJhenAiOiIyMTYyOTYwMzU4MzQtazFrNnFlMDYwczJ0cDJhMmphbTRsamRjbXMwMHN0dGcuYXBwcy5nb29nbGV1c2VyY29udGVudC5jb20iLCJhdWQiOiIyMTYyOTYwMzU4MzQtazFrNnFlMDYwczJ0cDJhMmphbTRsamRjbXMwMHN0dGcuYXBwcy5nb29nbGV1c2VyY29udGVudC5jb20iLCJzdWIiOiIxMDM4MDc4MzIzNTMyNTIzMDc3NDYiLCJlbWFpbCI6ImF3aW5odWFuZ0BnbWFpbC5jb20iLCJlbWFpbF92ZXJpZmllZCI6dHJ1ZSwibmJmIjoxNzA4MTQ1MjU3LCJuYW1lIjoiQXdpbiBIdWFuZyIsInBpY3R1cmUiOiJodHRwczovL2xoMy5nb29nbGV1c2VyY29udGVudC5jb20vYS9BQ2c4b2NJZjNQY0d3WjZIcDdYM204b3BjczRlNGVlZnBHQ1pGeVdMamExcjNTVVNKd1ZnPXM5Ni1jIiwiZ2l2ZW5fbmFtZSI6IkF3aW4iLCJmYW1pbHlfbmFtZSI6Ikh1YW5nIiwibG9jYWxlIjoiemgtVFciLCJpYXQiOjE3MDgxNDU1NTcsImV4cCI6MTcwODE0OTE1NywianRpIjoiNzBmNjI3NDFiNzhiYmVlMTYwNjBiZWRlOTY2YmFjYTAyZTY0ZTZkOSJ9.SXAVZ3SXny4YjIc9Cg6fNFHlXKe0jrm-4uwJ7KH41Tmo_vRAQGlbUn7MmVHXWexpKdpMCSVECC8C1VuUielC-vm8AoHMs1PLJCyhdg02hUyTqEMA08ydscfjguGP6kuI3LoMVsxkAl51C06lQi8llYZ4XGkdHxhCWP12fXQStdGPfv-64KNCkPTIfI7Teo7sfJGyjSQsDMRa4v9GWS9qmbCqut06fhpLyj0lEVfntratbuTN8ThekVfuJyJyG29U6xclm1O0NgBp-BnXML_YtBxTBV2Td_DRYY0dfcVivDKxzH135FfY5xpp_2ZIewkjJG5-pTHpin1R_XLVmIhXuA)
|
||||
- [Raspberry Pi 4 使用 Grafana 监控_influxdb and grafana on raspberrypi-CSDN博客](https://blog.csdn.net/u013360850/article/details/115568985)
|
||||
@@ -1,143 +0,0 @@
|
||||
## docker-compose.yml
|
||||
```yaml
|
||||
version: '3'
|
||||
|
||||
services:
|
||||
app:
|
||||
image: nextcloud
|
||||
ports:
|
||||
- 8080:80
|
||||
volumes:
|
||||
- ./data:/var/www/html
|
||||
restart: always
|
||||
```
|
||||
|
||||
## config.php
|
||||
Nextcloud 的 config 檔放在`/var/www/html/config/config.php`，對應到本機就是 `./data/config/config.php`，在安裝完成之後，需要修改 `trusted_domains`、`overwriteprotocol`、`overwrite.cli.url` 這幾個參數，如下：
|
||||
```php
|
||||
<?php
|
||||
$CONFIG = array (
|
||||
'htaccess.RewriteBase' => '/',
|
||||
'memcache.local' => '\\OC\\Memcache\\APCu',
|
||||
'apps_paths' =>
|
||||
array (
|
||||
0 =>
|
||||
array (
|
||||
'path' => '/var/www/html/apps',
|
||||
'url' => '/apps',
|
||||
'writable' => false,
|
||||
),
|
||||
1 =>
|
||||
array (
|
||||
'path' => '/var/www/html/custom_apps',
|
||||
'url' => '/custom_apps',
|
||||
'writable' => true,
|
||||
),
|
||||
),
|
||||
'memcache.distributed' => '\\OC\\Memcache\\Redis',
|
||||
'memcache.locking' => '\\OC\\Memcache\\Redis',
|
||||
'redis' =>
|
||||
array (
|
||||
'host' => 'redis',
|
||||
'password' => '',
|
||||
'port' => 6379,
|
||||
),
|
||||
'upgrade.disable-web' => true,
|
||||
'instanceid' => 'och3g4qo42hq',
|
||||
'passwordsalt' => 'kASfV5cf4Rh+EcvGNKQkmK01HD2UbI',
|
||||
'secret' => 'Vze6ZS+qgeOmacEn3ctbtV3uZaEpzeJDufjkkm4A9lgmUYpF',
|
||||
'trusted_domains' =>
|
||||
array (
|
||||
0 => 'nc.awin.one',
|
||||
),
|
||||
'datadirectory' => '/var/www/html/data',
|
||||
'dbtype' => 'mysql',
|
||||
'version' => '28.0.3.2',
|
||||
'dbname' => 'nextcloud',
|
||||
'dbhost' => 'db',
|
||||
'dbport' => '',
|
||||
'dbtableprefix' => 'oc_',
|
||||
'mysql.utf8mb4' => true,
|
||||
'dbuser' => 'nextcloud',
|
||||
'dbpassword' => 'F5vy&46Fzbn:hFnlHji.sWfS*SP~wC',
|
||||
'overwriteprotocol' => 'https',
|
||||
'overwrite.cli.url' => 'https://nc.awin.one',
|
||||
'maintenance_window_start' => 1,
|
||||
'default_phone_region' => 'TWN',
|
||||
'installed' => true,
|
||||
'mail_smtpmode' => 'smtp',
|
||||
'mail_sendmailmode' => 'smtp',
|
||||
'mail_from_address' => 'awinhuang',
|
||||
'mail_domain' => 'gmail.com',
|
||||
'mail_smtphost' => 'smtp.gmail.com',
|
||||
'mail_smtpport' => '587',
|
||||
'mail_smtpauth' => 1,
|
||||
'mail_smtpname' => 'awinhuang@gmail.com',
|
||||
'mail_smtppassword' => 'stcg ozpc ypsl enbp',
|
||||
'maintenance' => false,
|
||||
'loglevel' => 2,
|
||||
);
|
||||
```
|
||||
|
||||
## 遇到的問題
|
||||
1. 你經由安全的連線存取系統，但系統卻生成了不安全的 URL。這很有可能是因為你使用了反向代理伺服器，但反向代理伺服器的改寫規則並未正常工作，請閱讀關於此問題的文件頁面 ↗。
|
||||
1. 在 `config/config/php` 新增
|
||||
```
|
||||
'overwriteprotocol' => 'https',
|
||||
'overwrite.cli.url' => 'https://nc.awin.one',
|
||||
```
|
||||
這兩行
|
||||
|
||||
2. 增加 cron: `nextcloud_clean.sh` 在 crontab
|
||||
1. `*/5 * * * * /home/awin/script/nextcloud_clean.sh`
|
||||
|
||||
3. 伺服器未設定維護時段的開始時間。這代表了每天耗費大量資源的背景作業也會在您主要使用的時間內執行。我們建議將其設定為低使用率的時間，以減少使用者受到這些繁重任務帶來的負載影響。
|
||||
1. 在 `config/config/php` 增加 `'maintenance_window_start' => 1,`
|
||||
|
||||
4. 您並未設定手機國際冠碼。設定後使用者在個人檔案設定手機號碼時不必再輸入國際冠碼。若要這樣做，請新增「default_phone_region」至設定檔，允許的國家及地區請參閱 ISO 3166-1 code 清單。
|
||||
1. 在 `config/config/php` 增加 `'default_phone_region' => 'TWN',`
|
||||
|
||||
5. 您尚未為 WOPI 請求設定允許清單。若無此設定，使用者可以透過 WOPI 請求將受限制的檔案下載至 Nextcloud 伺服器
|
||||
|
||||
6. 此站台缺少一些建議的 PHP 模組。為了改善效能與相容性，強烈建立您安裝這些模組：bz2
|
||||
|
||||
7. How to know if redis is being used
|
||||
```
|
||||
docker exec -it redis /bin/sh
|
||||
cd
|
||||
redis-cli monitor
|
||||
ctrl+c
|
||||
```
|
||||
|
||||
8. gmail app password for nextcloud: `stcg ozpc ypsl enbp`
|
||||
|
||||
9. 大檔案無法上傳
|
||||
1. 改善傳輸的效率: `sudo docker exec -u 33 e84abbefd5ed php occ config:app:set files max_chunk_size --value 0`
|
||||
2. `docker-compose.yml` 要增加 3 個 environment：
|
||||
```yaml
|
||||
- PHP_MEMORY_LIMIT=10240M
|
||||
- PHP_UPLOAD_LIMIT=10240M
|
||||
- POST_MAX_SIZE=10240
|
||||
```
|
||||
3. ReverseProxy 要增加：
|
||||
|
||||
### 大檔案無法上傳
|
||||
1. 改善傳輸的效率: `sudo docker exec -u 33 e84abbefd5ed php occ config:app:set files max_chunk_size --value 0`
|
||||
2. `docker-compose.yml` 要增加 3 個 environment：
|
||||
```yaml
|
||||
- PHP_MEMORY_LIMIT=10240M
|
||||
- PHP_UPLOAD_LIMIT=10240M
|
||||
- POST_MAX_SIZE=10240
|
||||
```
|
||||
3. ReverseProxy 要增加：
|
||||
```yaml
|
||||
client_max_body_size 0;
|
||||
fastcgi_read_timeout 600;
|
||||
fastcgi_send_timeout 600;
|
||||
fastcgi_connect_timeout 600;
|
||||
proxy_connect_timeout 600;
|
||||
proxy_send_timeout 600;
|
||||
proxy_read_timeout 600;
|
||||
send_timeout 600;
|
||||
```````
|
||||
4. 上傳檔案時遇到 "server repliedL Not Found": `sudo docker exec -u 33 e84abbefd5ed php occ files:scan --all`
|
||||
@@ -1,26 +0,0 @@
|
||||
## Create a site
|
||||
Use `pelican-quickstart` to create a new site.
|
||||
|
||||
## Plugin
|
||||
```bash
|
||||
git clone --recursive https://github.com/getpelican/pelican-plugins.git
|
||||
```
|
||||
|
||||
## Theme
|
||||
先把所有佈景主題都clone下來：
|
||||
```bash
|
||||
git clone --recursive https://github.com/getpelican/pelican-themes.git
|
||||
```
|
||||
|
||||
把`pelicanconf.py`裡面的`THEME`指向theme的目錄就可以換佈景主題了。例如要用[[blue-penguin](https://github.com/jody-frankowski/blue-penguin)]這一個主題。把`pelicanconf.py`裡面加入`THEME = 'pelican-themes/blue-penguin'`就可以了。
|
||||
|
||||
## 預覽
|
||||
```
|
||||
make html
|
||||
make serve
|
||||
```
|
||||
|
||||
參考：
|
||||
- [koko's Note – Python - 安裝 Pelican Theme 來改變你的靜態網站主題](https://note.koko.guru/install-pelican-theme.html)
|
||||
- [nest theme](https://github.com/molivier/nest)
|
||||
- [Flex theme](https://github.com/alexandrevicenzi/Flex/wiki/Custom-Settings)
|
||||
@@ -1,260 +0,0 @@
|
||||
# 安裝
|
||||
## 下載ISO
|
||||
- [Get the free Proxmox VE ISO installer](https://www.proxmox.com/en/downloads/category/iso-images-pve)
|
||||
|
||||
## 準備USB disk
|
||||
- 用[Rufus](https://rufus.ie/)的話
|
||||
1. 在遇到詢問是否要下載 Grub 時，請選擇「否」
|
||||
2. 必須使用DD mode來建立開機碟。（參考：[Prepare Installation Media - Proxmox VE](https://pve.proxmox.com/wiki/Prepare_Installation_Media#_instructions_for_windows)）
|
||||
![[Pasted image 20210128212917.png]]
|
||||
|
||||
# 設定
|
||||
## 關閉「闔上螢幕後休眠」
|
||||
打開`/etc/systemd/logind.conf`：
|
||||
```
|
||||
nano /etc/systemd/logind.conf
|
||||
```
|
||||
找到下面兩行，把值改成ignore：
|
||||
```
|
||||
HandleLidSwitch=ignore
|
||||
HandleLidSwitchDocked=ignore
|
||||
```
|
||||
然後重開機：
|
||||
```
|
||||
systemctl restart systemd-logind.service
|
||||
```
|
||||
圖示：
|
||||
![[Pasted image 20210129194144.png]]
|
||||
|
||||
## 增加硬碟
|
||||
先用`lsblk`列出所有硬碟，這裡假設`sda`是我們的開機磁碟，我要要新增`sdb`：
|
||||
```
|
||||
root@pve:~# lsblk
|
||||
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
||||
sda 8:0 0 931.5G 0 disk <-- 目前在用的
|
||||
├─sda1 8:1 0 1007K 0 part
|
||||
├─sda2 8:2 0 512M 0 part
|
||||
└─sda3 8:3 0 931G 0 part
|
||||
sdb 8:16 0 111.8G 0 disk <-- 要新增的
|
||||
├─sdb1 8:17 0 100M 0 part
|
||||
├─sdb2 8:18 0 16M 0 part
|
||||
├─sdb3 8:19 0 111.1G 0 part
|
||||
└─sdb4 8:20 0 563M 0 part
|
||||
```
|
||||
|
||||
然後安裝`parted`，我們要用它來分割硬碟：
|
||||
```
|
||||
apt install parted
|
||||
```
|
||||
|
||||
開始分割：
|
||||
```
|
||||
parted /dev/sdb mklabel gpt
|
||||
```
|
||||
|
||||
建立primary partition，格式為`ext4`：
|
||||
```
|
||||
parted -a opt /dev/sdb mkpart primary ext4 0% 100%
|
||||
```
|
||||
|
||||
再來將分割好的硬碟格式化為`ext4`，label命名為`data2`：
|
||||
```
|
||||
mkfs.ext4 -L data2 /dev/sdb1
|
||||
```
|
||||
|
||||
再用`lsblk`看一次，會發現sdb已經重新分割成1個partition了：
|
||||
```
|
||||
root@pve:~# lsblk
|
||||
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
||||
sda 8:0 0 931.5G 0 disk
|
||||
├─sda1 8:1 0 1007K 0 part
|
||||
├─sda2 8:2 0 512M 0 part
|
||||
└─sda3 8:3 0 931G 0 part
|
||||
sdb 8:16 0 111.8G 0 disk
|
||||
└─sdb1 8:17 0 111.8G 0 part
|
||||
```
|
||||
|
||||
用`lsblk -fs`可以看到每一個硬碟的檔案系統格式：
|
||||
```
|
||||
root@pve:~# lsblk -fs
|
||||
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
|
||||
sda1 zfs_member rpool 11775123664036754029
|
||||
└─sda zfs_member rpool 11775123664036754029
|
||||
sda2 vfat rpool 32D0-3449
|
||||
└─sda zfs_member rpool 11775123664036754029
|
||||
sda3 zfs_member rpool 11775123664036754029
|
||||
└─sda zfs_member rpool 11775123664036754029
|
||||
sdb1 ext4 data2 bc6d2c41-a3ca-4b0f-a5de-51ee28ae9cec <-- 剛剛分割的
|
||||
└─sdb
|
||||
```
|
||||
|
||||
接下來，將新硬碟掛載到檔案目錄上，先建立一個新目錄來掛載新硬碟：
|
||||
```shell
|
||||
mkdir -p /mnt/data
|
||||
```
|
||||
|
||||
接下來編輯`/etc/fstab`，將新硬碟寫進來，這樣開機之後才會自動把它掛載起來：
|
||||
```
|
||||
nano /etc/fstab
|
||||
```
|
||||
加入這一行（注意：**data2**要改成你自己的label）：
|
||||
```
|
||||
LABEL=data2 /mnt/data ext4 defaults 0 2
|
||||
```
|
||||
|
||||
剛新硬碟掛起來：
|
||||
```
|
||||
mount -a
|
||||
```
|
||||
|
||||
用`df`就可以看到新硬碟了：
|
||||
```
|
||||
root@pve:~# df
|
||||
Filesystem 1K-blocks Used Available Use% Mounted on
|
||||
udev 16288892 0 16288892 0% /dev
|
||||
tmpfs 3262688 9324 3253364 1% /run
|
||||
rpool/ROOT/pve-1 942667136 1267584 941399552 1% /
|
||||
tmpfs 16313440 43680 16269760 1% /dev/shm
|
||||
tmpfs 5120 0 5120 0% /run/lock
|
||||
tmpfs 16313440 0 16313440 0% /sys/fs/cgroup
|
||||
rpool 941399680 128 941399552 1% /rpool
|
||||
rpool/data 941399680 128 941399552 1% /rpool/data
|
||||
rpool/ROOT 941399680 128 941399552 1% /rpool/ROOT
|
||||
/dev/fuse 30720 16 30704 1% /etc/pve
|
||||
tmpfs 3262688 0 3262688 0% /run/user/0
|
||||
/dev/sdb1 114854020 61464 108915208 1% /mnt/data <-- 新硬碟在這裡
|
||||
```
|
||||
|
||||
參考：
|
||||
- [How to add storage to Proxmox](https://nubcakes.net/index.php/2019/03/05/how-to-add-storage-to-proxmox/)
|
||||
|
||||
## 增加iSCSI磁碟
|
||||
### 增加需要CHAP認證的iSCSI磁碟
|
||||
1. 先確認找的到iSCSI磁碟
|
||||
```
|
||||
iscsiadm -m discovery -t st -p 192.168.1.11:3260
|
||||
```
|
||||
如果有找到的話會回傳一串IQN值，像是：
|
||||
```
|
||||
root@pve:~# iscsiadm -m discovery -t st -p 192.168.1.11:3260
|
||||
192.168.1.11:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.3e589efea3
|
||||
[fe80::211:32ff:fe20:eadd]:3260,1 iqn.2000-01.com.synology:DiskStation.Target-1.3e589efea3
|
||||
```
|
||||
2. 有IQN就可以用下列的命令連線與掛載：
|
||||
```
|
||||
iscsiadm -m node -T iqn.2000-01.com.synology:DiskStation.Target-1.3e589efea3 --op update --name node.session.auth.username --value=名字
|
||||
iscsiadm -m node -T iqn.2000-01.com.synology:DiskStation.Target-1.3e589efea3 --op update --name node.session.auth.password --value=密碼
|
||||
iscsiadm -m node -T iqn.2000-01.com.synology:DiskStation.Target-1.3e589efea3 -l #連線
|
||||
iscsiadm -m node -o update -n node.startup -v automatic #設定開機自動掛載
|
||||
```
|
||||
|
||||
## 增加NFS磁碟
|
||||
1. 先在Synology上開一個NFS disk，設定如下：
|
||||
![[Pasted image 20220506091522.png]]
|
||||
2. 再到Proxmox的 Datacenter->Storage->Add 來增加一個 *NFS*，設定如下
|
||||
![[Pasted image 20220506091624.png]]
|
||||
|
||||
### 更改NFS mount為soft
|
||||
1. 編輯`/etc/pve/storage.cfg`
|
||||
2. 做如下修改
|
||||
![[Pasted image 20220506095531.png]]
|
||||
|
||||
### 參考
|
||||
- [[經驗分享]Proxmox VE 採用 NFS 連接儲存的重點事項](http://blog.jason.tools/2019/02/pve-nfs-mount.html)
|
||||
|
||||
## 設定VM備份目錄
|
||||
如果將VM或LXC備份到某個目錄，先建立要備份的目錄：
|
||||
```shell
|
||||
mkdir -p /mnt/data/backup/
|
||||
```
|
||||
|
||||
再來用WEB UI，操作如下：
|
||||
![[Pasted image 20210129202041.png]]
|
||||
![[Pasted image 20210129202047.png]]
|
||||
|
||||
最後再到 Datacenter->Backups，建立一個scheule來備份就可以了：
|
||||
![[Pasted image 20210129202231.png]]
|
||||
|
||||
## 將資料備份到NAS
|
||||
1. 先在NAS開一個share folder跟一個帳號。
|
||||
![[Pasted image 20210202190402.png]]
|
||||
![[Pasted image 20210202190537.png]]
|
||||
2. Proxmox：到裡將剛剛新開的folder給掛載起來。
|
||||
![[Pasted image 20210202190640.png]]
|
||||
會跳出一個視窗，如下圖來填，記得**content**那一欄有4個要選。
|
||||
![[Pasted image 20210202190709.png]]
|
||||
3. Proxmox：到 Datacenter->Backup 新增一個排程。
|
||||
![[Pasted image 20210202190903.png]]
|
||||
一樣會跳出一個視窗，依需求來填，要注意的是**Storage**必須是前一步驟的**ID**，**Selection Mode**可以選擇**All**。
|
||||
![[Pasted image 20210202191150.png]]
|
||||
|
||||
參考：
|
||||
- [HASS + Proxmox: Automatic Backups to Synology NAS](https://kleypot.com/automatic-offline-backups/)
|
||||
|
||||
## 設定 UPS
|
||||
因為 UPS 的 USB 是連接在 NAS 上，所以Proxmox這邊必須要去monitor NAS那邊所回報的狀態，請確定NAS端有打開「啟用網路不斷電系統伺服器」。
|
||||
1. 安裝 nut：`apt-get install nut`
|
||||
2. 修改 `/etc/nut/nut.conf`，設定 `MODE=netclient`
|
||||
3. 修改 `/etc/nut/upsmon.conf`，加入一行：`MONITOR ups@<NAS_IP> 1 <NAS_Username> <NAS_UserPassword> slave`
|
||||
4. 開始 upsmon：`upsmon start`
|
||||
5. 用 `ps -ef | grep upsmon` 確認 upsmon是否執行：
|
||||
![[Pasted image 20220811145852.png|600]]
|
||||
6. 若正常，可以取回UPS的一些硬體資料，`upsc ups@<NAS_IP>`
|
||||
![[Pasted image 20220811150034.png|360]]
|
||||
|
||||
### 參考
|
||||
- [UPSMON(8)](https://networkupstools.org/docs/man/upsmon.html)
|
||||
- [不斷電系統 | DSM - Synology 知識中心](https://kb.synology.com/zh-tw/DSM/help/DSM/AdminCenter/system_hardware_ups?version=6)
|
||||
- [設定 Proxmox VE連動Synology的不斷電系統](https://cychien.tw/wordpress/2022/02/02/%E8%A8%AD%E5%AE%9A-proxmox-ve%E9%80%A3%E5%8B%95synology%E7%9A%84%E4%B8%8D%E6%96%B7%E9%9B%BB%E7%B3%BB%E7%B5%B1/)
|
||||
|
||||
## 更新
|
||||
### 加入更新來源
|
||||
編輯`/etc/apt/sources.list`，加入：
|
||||
```
|
||||
deb http://ftp.debian.org/debian bullseye main contrib
|
||||
deb http://ftp.debian.org/debian bullseye-updates main contrib
|
||||
|
||||
# PVE pve-no-subscription repository provided by proxmox.com,
|
||||
# NOT recommended for production use
|
||||
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
|
||||
|
||||
# security updates
|
||||
deb http://security.debian.org/debian-security bullseye-security main contrib
|
||||
```
|
||||
|
||||
### 取消訂閱服務
|
||||
編輯`/etc/apt/sources.list.d/pve-enterprise.list`，把下面這行注釋掉：
|
||||
```
|
||||
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
|
||||
```
|
||||
也就是變成：
|
||||
```
|
||||
#deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
|
||||
```
|
||||
|
||||
使用`apt update`來更新套件。
|
||||
使用`apt dist-upgrade`來升級系統版本。
|
||||
|
||||
## 重灌後要做的事情
|
||||
1. 建立ZFS pool。
|
||||
2. 確認S.M.A.R.T. 是否啟用，預設是啟用的。
|
||||
`smartctl -a /dev/<SDA_N>`
|
||||
1. 打開IOMMU
|
||||
2. 打開vm aware
|
||||
3. 增加NFS共享磁碟
|
||||
4. 排程備份
|
||||
5. 上傳安裝Windows需要的驅動ISO
|
||||
1. [Windows VirtIO Drivers](https://pve.proxmox.com/wiki/Windows_VirtIO_Drivers)
|
||||
6. 把常用的VM轉為template
|
||||
7. 安裝[Cockpit-Linux Server](https://pvecli.xuan2host.com/cockpit/), 讓您的PVE有更棒的圖形管理介面。
|
||||
|
||||
## 參考
|
||||
- [套件功能的更新（Proxmox update）](https://wiki.freedomstu.com/books/proxmox-ve-%E8%99%9B%E6%93%AC%E7%B3%BB%E7%B5%B1%E8%A8%98%E9%8C%84/page/%E5%A5%97%E4%BB%B6%E5%8A%9F%E8%83%BD%E7%9A%84%E6%9B%B4%E6%96%B0%EF%BC%88proxmox-update%EF%BC%89)
|
||||
- [裝完PVE後的11件必作清單 (中文翻譯)](https://www.youtube.com/watch?v=pY4Lm2Hoqik)
|
||||
- [Before I do anything on Proxmox, I do this first...](https://www.youtube.com/watch?v=GoZaMgEgrHw&t=0s)
|
||||
|
||||
# Trouble shooting
|
||||
- *Emergency mode*，表示開機失敗，請檢查`/etc/fstab`是不是有無法掛載的disk。
|
||||
|
||||
## 參考
|
||||
- [[Fix] Getting out of emergency mode : Proxmox](https://www.reddit.com/r/Proxmox/comments/hai75k/fix_getting_out_of_emergency_mode/)
|
||||
@@ -1,120 +0,0 @@
|
||||
# 步驟摘要
|
||||
1. 到[https://www.storj.io/host-a-node](https://www.storj.io/host-a-node)申請一個auth token。
|
||||
2. 用identify產生key。
|
||||
3. 認證 key。
|
||||
4. 備份 key
|
||||
5. Setup storj docker。
|
||||
6. Run storj docker。
|
||||
7. 更新
|
||||
|
||||
# 1. 申請一個auth token
|
||||
到[https://www.storj.io/host-a-node](https://www.storj.io/host-a-node)，填入email，會產生一個伴隨email的隨機碼。
|
||||
![[Pasted image 20240114200907.png]]
|
||||
|
||||
這一串要記下來。
|
||||
|
||||
# 用identify產生key
|
||||
## 下載
|
||||
### Windows
|
||||
下載 `https://github.com/storj/storj/releases/latest/download/identity_windows_amd64.zip`
|
||||
|
||||
### Linux
|
||||
#### X86
|
||||
```bash
|
||||
curl -L https://github.com/storj/storj/releases/latest/download/identity_linux_amd64.zip -o identity_linux_amd64.zip
|
||||
unzip -o identity_linux_amd64.zip
|
||||
chmod +x identity
|
||||
sudo mv identity /usr/local/bin/identity
|
||||
```
|
||||
|
||||
#### ARM
|
||||
```bash
|
||||
curl -L https://github.com/storj/storj/releases/latest/download/identity_linux_arm.zip -o identity_linux_arm.zip
|
||||
unzip -o identity_linux_arm.zip
|
||||
chmod +x identity
|
||||
sudo mv identity /usr/local/bin/identity
|
||||
```
|
||||
|
||||
## 產生 identity
|
||||
這一步會跑很久，建議用CPU比較強的來跑，在樹莓派上面會跑很久。
|
||||
|
||||
### Windows
|
||||
`./identity.exe create storagenode`
|
||||
|
||||
### Linux
|
||||
`identity create storagenode`
|
||||
|
||||
# 認證 Key
|
||||
## 認證
|
||||
等一下的 `<email:characterstring>` 就是第1步說要記起來的那一串
|
||||
|
||||
### Windows
|
||||
`./identity.exe authorize storagenode <email:characterstring>`
|
||||
|
||||
### Linux
|
||||
`identity authorize storagenode <email:characterstring>`
|
||||
|
||||
## 確認
|
||||
### Windows
|
||||
`(sls BEGIN "$env:AppData\Storj\Identity\storagenode\ca.cert").count` 應該要return 2
|
||||
`(sls BEGIN "$env:AppData\Storj\Identity\storagenode\identity.cert").count` 應該要return 3
|
||||
|
||||
### Linux
|
||||
`grep -c BEGIN ~/.local/share/storj/identity/storagenode/ca.cert` 應該要return 2
|
||||
`grep -c BEGIN ~/.local/share/storj/identity/storagenode/identity.cert` 應該要return 3
|
||||
|
||||
# 備份 key
|
||||
Windows 上產生的 key 會放在 `%APPDATA%\Storj\Identity\storagenode`。
|
||||
Linux 上產生的 key 會放在 `~/.local/share/storj/identity/storagenode`。
|
||||
記得備份。
|
||||
|
||||
# Setup storj docker
|
||||
Do this **once**.
|
||||
```bash
|
||||
sudo docker run --rm -e SETUP="true" \
|
||||
--mount type=bind,source="/home/awin/storj/key",destination=/app/identity \
|
||||
--mount type=bind,source="/home/awin/storj/data",destination=/app/config \
|
||||
--name storagenode storjlabs/storagenode:latest
|
||||
```
|
||||
|
||||
# Run storj docker
|
||||
```bash
|
||||
sudo docker run -d --restart always --stop-timeout 300 \
|
||||
-p 28967:28967/tcp \
|
||||
-p 28967:28967/udp \
|
||||
-p 14002:14002 \
|
||||
-e WALLET="0x9Ce80345355Ad8C17991620E13d8423900CEDcd0" \
|
||||
-e EMAIL="awinhuang@gmail.com" \
|
||||
-e ADDRESS="storj.awin.one:28967" \
|
||||
-e STORAGE="1800GB" \
|
||||
--memory=800m \
|
||||
--log-opt max-size=50m \
|
||||
--log-opt max-file=10 \
|
||||
--sysctl net.ipv4.tcp_fastopen=3 \
|
||||
--mount type=bind,source=/home/awin/storj/key,destination=/app/identity \
|
||||
--mount type=bind,source=/extusb1/storj,destination=/app/config \
|
||||
--name storagenode storjlabs/storagenode:latest
|
||||
```
|
||||
|
||||
# 更新
|
||||
更新 node 可以選擇用 docker 裝[storjlabs/watchtower](https://hub.docker.com/r/storjlabs/watchtower/tags) ，或是手動更新
|
||||
|
||||
## watchtower
|
||||
```shell
|
||||
sudo docker pull storjlabs/watchtower
|
||||
sudo docker run -d --restart=always --name watchtower -v /var/run/docker.sock:/var/run/docker.sock storjlabs/watchtower storagenode watchtower --stop-timeout 300s
|
||||
```
|
||||
|
||||
等 [[Watchtower|Watchtower]] 跑起來之後，可以用 `sudo docker exec -it storagenode /app/dashboard.sh` 來即時觀察執行流量。
|
||||
|
||||
## 手動
|
||||
```shell
|
||||
sudo docker stop -t 300 storagenode
|
||||
sudo docker rm storagenode
|
||||
sudo docker pull storjlabs/storagenode:latest
|
||||
```
|
||||
|
||||
# 參考
|
||||
- [Step 2. Get an Authorization Token - Storj Docs](https://docs.storj.io/node/get-started/auth-token)
|
||||
- [Step 5. Create an Identity - Storj Docs](https://docs.storj.io/node/get-started/identity)
|
||||
- [Install storagenode on Raspberry Pi3 or higher version – Storj](https://support.storj.io/hc/en-us/articles/360026612332-Install-storagenode-on-Raspberry-Pi3-or-higher-version)
|
||||
@@ -1,25 +0,0 @@
|
||||
{
|
||||
"nodes":[
|
||||
{"id":"c910b905ac74e6ac","type":"group","x":20,"y":-700,"width":660,"height":860,"label":"Dockers"},
|
||||
{"id":"07f9200cb8cda96b","type":"group","x":340,"y":-360,"width":320,"height":362,"label":"grafana"},
|
||||
{"id":"6156176d915b8a66","type":"group","x":340,"y":-640,"width":320,"height":220,"label":"Nextcloud"},
|
||||
{"id":"f33aa20a0c8167ec","type":"text","text":"### blog\n- \"8010:80\"","x":40,"y":-445,"width":280,"height":90},
|
||||
{"id":"7ac25f505df8f886","type":"text","text":"### portainer\n- 8000:8000\n- 2443:9443","x":40,"y":-560,"width":280,"height":100},
|
||||
{"id":"f68bc5941384884f","type":"text","text":"### nginx-certbot\n- 80:80\n- 443:443","x":40,"y":-680,"width":280,"height":100},
|
||||
{"id":"daa7f9a1b63e3a74","type":"text","text":"### nextcloud\n- 8080:80","x":360,"y":-620,"width":280,"height":80},
|
||||
{"id":"5f777bb386a0b8aa","type":"text","text":"### collabora\n- 8081:9980","x":360,"y":-525,"width":280,"height":85},
|
||||
{"id":"8d78e0acaa9616d5","type":"text","text":"### adguardhome\n- \"53:53/tcp\"\n- \"53:53/udp\"\n- \"3000:3000/tcp\"\n- \"8050:80/tcp\"","x":40,"y":-120,"width":280,"height":160},
|
||||
{"id":"41ec11c5704a134c","type":"text","text":"### freshrss\n- \"8070:1200\"","x":40,"y":60,"width":280,"height":80},
|
||||
{"id":"5f8a89afeef02f38","type":"text","text":"### openspeedtest\n- '8093:3000'\n- '8094:3001'","x":360,"y":35,"width":280,"height":105},
|
||||
{"id":"4b08c3fa2d3fe2cf","type":"text","text":"### gitea\n- \"8020:3000\"\n- \"2244:22\"","x":40,"y":-340,"width":280,"height":100},
|
||||
{"id":"b112aedbb6b5ce68","type":"text","text":"### filebrowser\n- 8040:80","x":40,"y":-220,"width":280,"height":80},
|
||||
{"id":"5c65ba78253b985b","type":"text","text":"### AWIN-PC2\n`192.168.1.24`","x":-240,"y":-260,"width":180,"height":80,"color":"2"},
|
||||
{"id":"c0c54f342022f6db","type":"text","text":"### grafana\n- \"8082:3000\"","x":360,"y":-340,"width":280,"height":75},
|
||||
{"id":"520020bcf81de93b","type":"text","text":"### prometheus\n- \"8083:9090\"","x":360,"y":-240,"width":280,"height":90},
|
||||
{"id":"59d436dadba47e3c","type":"text","text":"### node_exporter\n- \"8084:9100\"","x":360,"y":-120,"width":280,"height":102},
|
||||
{"id":"ae5e0200e802c0ff","x":720,"y":-640,"width":250,"height":100,"type":"text","text":"### Minecraft\n- 8100"}
|
||||
],
|
||||
"edges":[
|
||||
{"id":"2155d66680f8b2ba","fromNode":"5c65ba78253b985b","fromSide":"right","toNode":"c910b905ac74e6ac","toSide":"left"}
|
||||
]
|
||||
}
|
||||
@@ -1,52 +0,0 @@
|
||||
# docker-compose.yml
|
||||
```yml
|
||||
version: '3'
|
||||
services:
|
||||
file-browser:
|
||||
restart: always
|
||||
image: filebrowser/filebrowser:latest
|
||||
container_name: filebrowser
|
||||
user: 1000:1000
|
||||
ports:
|
||||
- 8040:80
|
||||
volumes:
|
||||
- /media/share:/srv
|
||||
- ./data/filebrowser.db:/database.db
|
||||
- ./data/settings.json:/.filebrowser.json
|
||||
- ./data/gafiled.png:/config/logo.png
|
||||
- ./data/branding:/branding
|
||||
security_opt:
|
||||
- no-new-privileges:true
|
||||
```
|
||||
|
||||
# 準備
|
||||
在 `docker compose up -d` 之前，需要先把檔案準備好。
|
||||
```shell
|
||||
touch data/filebrowser.db
|
||||
touch data/settings.json
|
||||
```
|
||||
|
||||
`data/settings.json` 的內容：
|
||||
```json
|
||||
{
|
||||
"port": 80,
|
||||
"baseURL": "",
|
||||
"address": "",
|
||||
"log": "stdout",
|
||||
"database": "/database.db",
|
||||
"root": "/srv"
|
||||
}
|
||||
```
|
||||
|
||||
# 登入
|
||||
預設的帳號密碼是`admin/admin`，記得要改掉。
|
||||
|
||||
# 問題
|
||||
因為Filebrowser會lock DB，所以docker在跑得時候會無法使用Filebrowser的command，所以需要先把docker停掉，然後用以下命令登入：
|
||||
```shell
|
||||
sudo docker run -it -v ./data/filebrowser.db:/database.db -v data/settings.json:/.filebrowser.json --entrypoint /bin/sh filebrowser/filebrowser
|
||||
```
|
||||
|
||||
# 參考
|
||||
- [Filebrowser Docker Installation | All about](https://bobcares.com/blog/filebrowser-installation-in-docker/)
|
||||
- [filebrowser/filebrowser: 📂 Web File Browser](https://github.com/filebrowser/filebrowser)
|
||||
@@ -1,26 +0,0 @@
|
||||
```yml
|
||||
version: "3"
|
||||
|
||||
services:
|
||||
freshrss:
|
||||
image: linuxserver/Taipei:latest
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "8080:80"
|
||||
environment:
|
||||
TZ: Asia/Shanghai
|
||||
CRON_MIN: "*/60"
|
||||
PUID: 1000
|
||||
PGID: 1000
|
||||
volumes:
|
||||
- freshrss_data:/var/www/FreshRSS/data
|
||||
- freshrss_extensions:/var/www/FreshRSS/extensions
|
||||
|
||||
rsshub:
|
||||
image: diygod/rsshub:latest
|
||||
restart: unless-stopped
|
||||
expose:
|
||||
- "1200"
|
||||
environment:
|
||||
CACHE_EXPIRE: 3600
|
||||
```
|
||||
@@ -1,41 +0,0 @@
|
||||
# `docker-compose.yml`
|
||||
|
||||
```yml
|
||||
services:
|
||||
minecraft:
|
||||
image: itzg/minecraft-server
|
||||
restart: unless-stopped
|
||||
tty: true
|
||||
stdin_open: true
|
||||
ports:
|
||||
- "8100:25565"
|
||||
environment:
|
||||
MEMORY: "16G" # 設定分配16GB RAM
|
||||
JVM_OPTS: "-XX:MaxRAMPercentage=75" # 設定JVM啟動參數，設定最多使用75% RAM
|
||||
|
||||
EULA: "TRUE" # 自動同意伺服器的EULA
|
||||
TYPE: "PAPER"
|
||||
VERSION: "1.19.4"
|
||||
MAX_BUILD_HEIGHT: 384
|
||||
VIEW_DISTANCE: 12
|
||||
MODE: "creative"
|
||||
ENABLE_WHITELIST: "TRUE"
|
||||
ENFORCE_WHITELIST: "TRUE"
|
||||
OPS: ""
|
||||
ONLINE_MODE: "TRUE"
|
||||
SERVER_NAME: "Crazy Smile City"
|
||||
MOTD: "Today is a good day~~~"
|
||||
ICON: ""
|
||||
OVERRIDE_SERVER_PROPERTIES: "TRUE"
|
||||
TZ:
|
||||
- /etc/localtime:/etc/localtime:ro
|
||||
- /etc/timezone:/etc/timezone:ro
|
||||
volumes:
|
||||
- ./data:/data
|
||||
```
|
||||
|
||||
# 參考
|
||||
- [如何在Ubuntu系統以Docker架設Minecraft Java版伺服器 · Ivon的部落格](https://ivonblog.com/posts/minecraft-java-edition-server-docker/)
|
||||
- [Docker Minecraft 开服记](https://blog.l3zc.com/2023/06/build-a-mc-server-with-docker/#%E8%BF%9B%E4%B8%80%E6%AD%A5%E8%B0%83%E6%95%B4)
|
||||
- [Variables - Minecraft Server on Docker (Java Edition)](https://docker-minecraft-server.readthedocs.io/en/latest/variables/#server)
|
||||
-
|
||||
@@ -1,32 +0,0 @@
|
||||
# 看硬碟代號
|
||||
```
|
||||
lsblk
|
||||
```
|
||||
```result
|
||||
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
|
||||
sda 8:0 0 1.8T 0 disk
|
||||
└─sda1 8:1 0 1.8T 0 part /extusb1/storj
|
||||
mmcblk0 179:0 0 14.6G 0 disk
|
||||
├─mmcblk0p1 179:1 0 256M 0 part /boot
|
||||
└─mmcblk0p2 179:2 0 14.3G 0 part /
|
||||
```
|
||||
衍生出來的`sda1`、`mmcblk0p1`、`mmcblk0p2` 之類的就是硬碟代號
|
||||
|
||||
# 格式化
|
||||
```bash
|
||||
sudo mkfs.ext4 /dev/sdb123 # sdb123 要換成你自己的硬碟代號
|
||||
```
|
||||
|
||||
# 掛載硬碟
|
||||
```
|
||||
sudo mount <硬碟代號> <路徑>
|
||||
```
|
||||
|
||||
例如：
|
||||
```
|
||||
sudo mount /dev/sda1 /home/user/myusb
|
||||
```
|
||||
就是把`/dev/sda1` 掛載到 `/home/user/myusb` 這個目錄下面。
|
||||
|
||||
# 開機自動掛載硬碟
|
||||
![[開機自動掛載硬碟]]
|
||||
@@ -1,6 +0,0 @@
|
||||
在 `/etc/modules-load.d` 開一個檔案叫做 `nct6683.conf`，裡面填入：
|
||||
```
|
||||
nct6683
|
||||
```
|
||||
|
||||
下一次開機的時候，系統就會自動載入 `nct6683` 這個模組了。
|
||||
@@ -1,10 +0,0 @@
|
||||
要開機自動掛載的話，需要知道你要掛載硬碟的UUID，然後把它填到 `/etc/fstab` 就可以了。
|
||||
|
||||
用 `blkid` 來看 UUID:
|
||||
![[20240228_170818_WindowsTerminal_1733x303.png]]
|
||||
然後在 `/etc/fstab` 加入一行：
|
||||
```
|
||||
UUID=be92f54f-e427-496e-83e9-a29643aa5af0 /lvm1 ext4 defaults,nofail 0 2
|
||||
```
|
||||
|
||||
關於 `/etc/fstab` 詳細請再看：[[fstab]]
|
||||
Reference in New Issue
Block a user