闲置手机搭建linux系统并安装docker

1、安装alpineterm#

Alpine-termux是APP，Alpine系统是Alpine-termux APP中的一个虚拟机，你可以将Alpine-termux理解为VMware或者Hyper-V或其它虚拟机软件，而Alpine是在虚拟机里运行的Linux系统。

GitHub项目页：https://github.com/FakeRajbhx/alpine-term

2、初始化和登录#

下载安装后初始化开机，开机后，登录系统，用户：alpine 密码: alpine 切换到root账户，输入sudo -s 密码为 alpine ，接着修改root密码，输入 passwd ，需要输入两次密码。

3、ssh和root配置#

vi /etc/ssh/sshd_config配置文件，将PasswordAuthentication和PermitRootLogin的no改成yes

或者

系统默认是禁止ssh密码登录的，所以需要先开启它，输入：

1
sed -i ‘s/PasswordAuthentication no/PasswordAuthentication yes/g’ /etc/ssh/sshd_config

开启root用户登录的话，输入

1
sed -i ‘s/PermitRootLogin no/PermitRootLogin yes/g’ /etc/ssh/sshd_config

然后重启启动sshd服务，输入

1
service sshd restart

4、alpine到termux的端口映射#

映射ssh的22端口（方便电脑操作，只想手机操作就忽略这个步骤），因为是Qemu套娃，所以需要映射ssh的22端口，开机完成后，手指在软件的左上方向右滑，会出现菜单。

选择[2]/dev/ttyS0，输入下列代码映射ssh的22端口到手机的8022端口

1
ssh root@127.0.0.1 -p 22

选择 [1]QEMU

1
hostfwd_add tcp::8022-:22

【注意事项1】这个映射端口的命令每次重启Alpine Term 都需要重新设置一次，建议常驻后台。执行上面的指令后就可以远程ssh手机的8022端口。这样当手机和电脑处于同一局域网的时候我们就能在电脑上通过FinalShell远程登录手机的Termux模拟终端了。在电脑上操作终端复制命令比较方便。

【注意事项2】如果你中途出门去公司或其它公共场合，连接了其它wifi，只要没主动关闭Alpine Term APP后台，可以直接在wifi设置里查看新的IP，使用新IP+8022访问模拟终端。

5、网络配置#

在alpine中，使用vi编辑器：

1
vi /etc/network/interfaces

添加如下配置，这里使用dhcp自动获取IP，Alpine虚拟机在这种套娃式的情境下没必要设置固定IP。

1
auto lo
2
iface lo inet loopback
3
auto eth0
4
iface eth0 inet dhcp

保存后重启网络

1
/etc/init.d/networking restart

配置DNS地址（不配也行）

1
vi /etc/resolv.conf

添加如下配置

1
nameserver 8.8.8.8
2
nameserver 8.8.4.4

resolv.conf修改后没有重启操作，直接就生效了！这样alpine就能访问互联网了，如果还是没网，就重启APP重新配置！

6、配置APK源#

查看系统版本

1
cat /etc/alpine-release
2
3.13.0

方案一、使用阿里镜像 https://mirrors.aliyun.com

1
sed -i 's/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g' /etc/apk/repositories

方案二、使用科大镜像 http://mirrors.ustc.edu.cn

1
sed -i 's/dl-cdn.alpinelinux.org/mirrors.ustc.edu.cn/g' /etc/apk/repositories

在上面方案中找到对应系统版本的源版本，这里使用阿里云的镜像源https://mirrors.aliyun.com/alpine/v3.13/

找到的源写入以下文件

1
vi /etc/apk/repositories

文件内容修改为以下信息

1
# Main package repositories.
2
https://mirrors.aliyun.com/alpine/v3.13/main
3
https://mirrors.aliyun.com/alpine/v3.13/community
4

5
# Testing repository.
6
# You can install packages from this repository with:
7
# apk add package@testing
8
@testing https://mirrors.aliyun.com/alpine/v3.13/main

或者也可以使用sed替换

1
sed -i 's/文本/文本/g' /etc/apk/repositories

更新仓库

1
apk update

升级软件包，后面加–force-broken-world跳过一些问题

1
apk upgrade --available --force-broken-world

7、重新进入系统#

启动alpine-term APP后等待系统加载完成。

系统加载完成后使用root用户登录系统：

1
root/xxxxx

之后在alpine系统命令行输入：

1
ssh root@127.0.0.1 -p 22

然后手指在软件的左上方向右滑，进行端口映射，选择 [1]QEMU输入：

1
hostfwd_add tcp::8022-:22

之后就可以在电脑端使用alpine-term IP加上8022远程访问alpine系统了。

8、安装docker#

正常安装：#

安装docker

1
sudo apk add docker

使docker开机启动

1
sudo rc-update add docker

开启docker服务

1
sudo service docker start

后台启动

1
sudo setsid containerd
2

3
sudo setsid dockerd

寻找错误：#

无法启动，可以查看日志，寻找错误原因

1
cat /var/log/docker.log

docker启动报错，错误表明在尝试挂载 Overlay2 存储驱动时出现了问题

1
"failed to mount overlay: no such device storage-driver=overlay2"

添加以下文件及信息

1
vi /etc/docker/daemon.json

1
{
2
  "storage-driver": "overlay2"
3
}

输入命令查看驱动器是否存在

1
docker info | grep "Storage Driver"

输出应为

1
Storage Driver: overlay2

输出为空？安装适配的 Alpine Linux 内核模块包：

1
sudo apk add linux-virt linux-virt-dev

之后重启系统：（也许需要重新映射端口，即重新配置7、ssh）

1
reboot

测试

1
docker info
2
docker ps

测试成功的信息

1
root@alpine-term ~ # docker info
2
Client:
3
 Context:    default
4
 Debug Mode: false
5

6
Server:
7
 Containers: 0
8
  Running: 0
9
  Paused: 0
10
  Stopped: 0
11
 Images: 0
12
 Server Version: 20.10.3
13
 Storage Driver: overlay2
14
  Backing Filesystem: extfs
15
  Supports d_type: true
16
  Native Overlay Diff: true
17
 Logging Driver: json-file
18
 Cgroup Driver: cgroupfs
19
 Cgroup Version: 1
20
 Plugins:
21
  Volume: local
22
  Network: bridge host ipvlan macvlan null overlay
23
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
24
 Swarm: inactive
25
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
26
 Default Runtime: runc
27
 Init Binary: docker-init
28
 containerd version: 7eba5930496d9bbe375fdf71603e610ad737d2b2
29
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
30
 init version:
31
 Security Options:
32
  seccomp
33
   Profile: default
34
 Kernel Version: 5.10.152-0-virt
35
 Operating System: Alpine Linux v3.13
36
 OSType: linux
37
 Architecture: x86_64
38
 CPUs: 1
39
 Total Memory: 2.336GiB
40
 Name: alpine-term
41
 ID: XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX(其他数据)
42
 Docker Root Dir: /var/lib/docker
43
 Debug Mode: false
44
 Registry: https://index.docker.io/v1/
45
 Labels:
46
 Experimental: false
47
 Insecure Registries:
48
  127.0.0.0/8
49
 Live Restore Enabled: false
50

51
WARNING: No blkio weight support
52
WARNING: No blkio weight_device support

9、安装docker compose#

curl可能会因为alpine系统网络问题无法下载

1
curl -SL https://github.com/docker/compose/releases/download/v2.23.3/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose

直接去PC浏览器下载，然后再通过终端上传到alpine系统

1
https://github.com/docker/compose/releases/download/v2.23.3/docker-compose-linux-x86_64

下载完成后将其上传到目录/usr/local/bin/，修改docker-compose-linux-x86_64为docker-compose

1
cd /usr/local/bin/
2
mv docker-compose-linux-x86_64 docker-compose

修改docker-compose权限

1
chmod 777 docker-compose
2
#或者是
3
chmod +x /usr/local/bin/docker-compose

查看docker-compose版本

1
docker-compose -v
2
Docker Compose version v2.23.3

10、部署个人网盘#

前言：因为Alpine-termux APP和手机本身的限制，有时候拉取镜像会因为网络的问题直接失败。

1
root@alpine-term /mnt/shared/h1d/kodbox # docker-compose up -d
2
[+] Running 0/39
3
⠋ db 8 layers [⠀⠀⠀⠀⠀⠀⠀⠀] 0B/0B Pulling 27.9s
4
⠧ d4c3c94e5e10 Waiting 13.6s
5
error pulling image configuration: Get "https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/d7/d7a7b84914e9e8f30bd2d3a4114a65dcc076982658d77dce2471f7a8680556ab/data?verify=1715396819-pzw5%2BKmSVyKpEVAUKLWXjUiz93M%3D": net/http: TLS handshake timeout

所以这里我放弃了在Alpine-termux APP虚拟机里直接拉取镜像。我在电脑端起了一台centos7虚拟机，在centos7中执行docker-compose pull镜像。

1、vmware PC环境（容器部署与迁移）

1.在centos7中安装docker

安装并启动docker服务, 新版本docker会自动安装docker-compose-plugin

1
 curl -fsSL https://get.docker.com | bash -s docker --mirror Aliyun
2
 systemctl enable docker && systemctl start docker

docker compose 用法, 在通过docker compose up启动后, 可以使用docker compose ls查看配置文件位置

1
docker compose ls

提示：若docker compose命令不存在，可手动安装二进制文件docker-compose并在后续命令中替换。

1
curl -SL https://github.com/docker/compose/releases/download/v2.23.3/docker-compose-linux-x86_64 -o /usr/local/bin/docker-compose
2
chmod +x /usr/local/bin/docker-compose

2.http方式快速启动

注意：

首先创建一个目录作为项目目录，后面所有命令都在这个目录下执行

1
mkdir /kodbox && cd /kodbox

需在db.env中设置数据库密码，还有yml中的MYSQL_ROOT_PASSWORD需补充.

创建文件来设置数据库环境变量vim db.env

1
MYSQL_PASSWORD=test@123
2
MYSQL_DATABASE=kodbox
3
MYSQL_USER=kodbox

创建docker-compose.yml 文件

1
 vim docker-compose.yml

在其中配置映射端口、持久化目录

1
version: '3.5'
2

3
services:
4
  db:
5
    image: mariadb:10.6
6
    restart: always
7
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
8
    volumes:
9
      - "./db:/var/lib/mysql"       #./db是数据库持久化目录，可以修改
10
      # - "./etc/mysql/conf.d:/etc/mysql/conf.d"       #增加自定义mysql配置
11
    environment:
12
      - MYSQL_ROOT_PASSWORD=test@123
13
      - MARIADB_AUTO_UPGRADE=1
14
      - MARIADB_DISABLE_UPGRADE_BACKUP=1
15
    env_file:
16
      - db.env
17

18
  app:
19
    image: kodcloud/kodbox
20
    restart: always
21
    ports:
22
      - 8082:80                       #左边8082是使用端口，可以修改
23
    volumes:
24
      - "./site:/var/www/html"      #./site是站点目录位置，可以修改
25
    environment:
26
      - MYSQL_HOST=db
27
      - REDIS_HOST=redis
28
    env_file:
29
      - db.env
30
    depends_on:
31
      - db
32
      - redis
33

34
  redis:
35
    image: redis:alpine
36
    restart: always

增加自定义mysql配置：

mkdir -p ./etc/mysql/conf.d && vim ./etc/mysql/conf.d/custom.cnf

进入项目目录，执行docker compose up -d启动命令，会自动拉取容器并运行

1
docker compose up -d

1
[root@localhost kodbox]# docker compose up -d
2
WARN[0000] /kodbox/docker-compose.yml: `version` is obsolete
3
[+] Running 21/24
4
[+] Running 24/24
5
 ✔ redis Pulled
6
 ✔ db Pulled
7
 ✔ app Pulled
8
   ✔ 4abcf2066143 Already exists
9
   ✔ 4b99432ace8a Pull complete
10
   ✔ d3a73aae1c86 Pull complete
11
   ✔ 9294d9185d89 Pull complete
12
   ✔ 0150bd92669e Pull complete
13
   ✔ 036a86a4ae38 Pull complete
14
   ✔ 75d2a8eea798 Pull complete
15
   ✔ 23484683932f Pull complete
16
   ✔ b8f832e65336 Pull complete
17
   ✔ b483e4a592eb Pull complete
18
   ✔ 3a7dde3951ca Pull complete
19
   ✔ cfe5bc492e21 Pull complete
20
   ✔ 3a23c501ebe9 Pull complete
21
   ✔ 048b5f93008a Pull complete
22
   ✔ c4a1cf1fe966 Pull complete
23
   ✔ 636b4e8a2c46 Pull complete
24
   ✔ fed06c53db4e Pull complete
25
   ✔ 179134eaf663 Pull complete
26
   ✔ a5ce73d87f31 Pull complete
27
   ✔ cb96a54eed25 Pull complete
28
   ✔ 17f2e044ddce Pull complete
29
[+] Running 3/3
30
 ✔ Container kodbox-redis-1  Started
31
 ✔ Container kodbox-db-1     Started
32
 ✔ Container kodbox-app-1    Started

查看启动的容器

1
[root@localhost kodbox]# docker ps
2
CONTAINER ID   IMAGE             COMMAND                  CREATED              STATUS              PORTS                                                      NAMES
3
85204045b448   kodcloud/kodbox   "/entrypoint.sh supe…"   About a minute ago   Up About a minute   443/tcp, 9000/tcp, 0.0.0.0:8082->80/tcp, :::8082->80/tcp   kodbox-app-1
4
d5b5ab5e725b   mariadb:10.6      "docker-entrypoint.s…"   About a minute ago   Up About a minute   3306/tcp                                                   kodbox-db-1
5
2d376d5abc17   redis:alpine      "docker-entrypoint.s…"   7 days ago           Up About a minute   6379/tcp

访问页面：http://IP:8082

进入页面说明容器运行正常！

现在回到centos7虚拟机停止容器，用不上也可以直接删除容器

1
docker compose down

或者

1
docker stop $(docker ps -aq)

现在开始做镜像迁移的工作

查看镜像

1
[root@localhost kodbox]# docker images
2
REPOSITORY        TAG       IMAGE ID       CREATED        SIZE
3
kodcloud/kodbox   latest    58cb616b43ad   7 hours ago    405MB
4
mariadb           10.6      d7a7b84914e9   2 months ago   396MB
5
redis             alpine    435993df2c8d   4 months ago   41MB

打包镜像

1
[root@localhost kodbox]# docker save kodcloud/kodbox -o kodcloud.tar.gz
2
[root@localhost kodbox]# docker save mariadb -o mariadb.tar.gz
3
[root@localhost kodbox]# docker save redis -o redis.tar
4
[root@localhost kodbox]# ls
5
db  db.env  docker-compose.yml  etc  kodcloud.tar.gz  mariadb.tar.gz  redis.tar  site

通过终端将上面三个tar包下载到电脑上

2、Alpine-termux APP环境（容器加载与启用）

这时候就可以回到Alpine-termux APP了。在Alpine-termux APP终端界面，也就是在电脑上远程访问的Alpine-termux APP的终端。将刚刚下载的三个tar包上传到/mnt/shared/kodbox目录，没有kodbox目录就创建一个。上传完毕，就可以将三个tar包加载到Alpine-termux虚拟机的Docker中了。加载比较慢，准备好小风扇和耐心，小风扇用来给手机降温，耐心就是起来喝杯水，活动活动！20分钟以内可以load完毕，具体看你的手机性能。

1
root@alpine-term /mnt/shared/kodbox/kodbox # ls
2
kodcloud.tar.gz  mariadb.tar.gz  redis.tar
3
root@alpine-term /mnt/shared/kodbox/kodbox # docker load -i kodcloud.tar.gz
4
0d132584d8c5: Loading layer [==================================================>]  4.608kB/4.608kB
5
624532f7ccc6: Loading layer [==================================================>]  16.64MB/16.64MB
6
db5380e6eb60: Loading layer [==================================================>]  29.18kB/29.18kB
7
5aac726471b9: Loading layer [==================================================>]  117.7MB/117.7MB
8
d232fe2802e2: Loading layer [==================================================>]  11.78kB/11.78kB
9
Loaded image: kodcloud/kodbox:latest
10
root@alpine-term /mnt/shared/kodbox/kodbox # docker load -i mariadb.tar.gz
11
4a1518ebc26e: Loading layer [==================================================>]  75.19MB/75.19MB
12
83f847955cac: Loading layer [==================================================>]  337.9kB/337.9kB
13
9fdf21bd2866: Loading layer [==================================================>]  19.82MB/19.82MB
14
5e288c3023fb: Loading layer [==================================================>]  1.536kB/1.536kB
15
cec328595a1a: Loading layer [==================================================>]   5.12kB/5.12kB
16
4f0916a5998c: Loading layer [==================================================>]  306.7MB/306.7MB
17
dc6ebc95f266: Loading layer [==================================================>]   12.8kB/12.8kB
18
d5edc3bae6d4: Loading layer [==================================================>]  29.18kB/29.18kB
19
Loaded image: mariadb:10.6
20
root@alpine-term /mnt/shared/kodbox/kodbox # docker load -i redis.tar
21
cc28a282a293: Loading layer [==================================================>]  11.78kB/11.78kB
22
4afac1336e0b: Loading layer [==================================================>]  1.986MB/1.986MB
23
442071c42c46: Loading layer [==================================================>]  2.445MB/2.445MB
24
ea9ee74b2076: Loading layer [==================================================>]  30.08MB/30.08MB
25
fdb08b0a99f7: Loading layer [==================================================>]  1.536kB/1.536kB
26
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
27
575a330fe53e: Loading layer [==================================================>]  4.096kB/4.096kB
28
Loaded image: redis:alpine

加载完镜像后，查看docker镜像。

完美，镜像已经成功导入docker了。

1
root@alpine-term /mnt/shared/kodbox/kodbox # docker images
2
REPOSITORY        TAG       IMAGE ID       CREATED        SIZE
3
kodcloud/kodbox   latest    58cb616b43ad   8 hours ago    405MB
4
mariadb           10.6      d7a7b84914e9   2 months ago   396MB
5
redis             alpine    435993df2c8d   4 months ago   41MB

现在还不能立马启动镜像，因为/mnt/shared目录虽然空间大，但是它本身是手机的系统目录，所以这里会有权限问题。

这个/mnt/shared目录导致的权限问题会让mariadb容器无法find /var/lib/mysql目录。

所以/mnt/shared目录也就是临时用来存放一下较大的镜像。

在我之前的实验中mariadb容器就报出了find: ‘/var/lib/mysql/’: Operation not permitted的问题！

1
root@alpine-term /mnt/shared/kodbox # docker logs -f --tail 500 5286394745f4
2
2024-05-11 03:55:19+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.17+maria~ubu2004 started.
3
find: ‘/var/lib/mysql/’: Operation not permitted

所以这里不能在/mnt/shared目录创建docker-compose.yml文件。

回到home目录，在home目录下创建kodbox目录。

这里执行部分之前在centos7虚拟机中的操作步骤。

创建db.env文件

1
vim db.env

写入内容

1
MYSQL_PASSWORD=test@123
2
MYSQL_DATABASE=kodbox
3
MYSQL_USER=kodbox

创建docker-compose.yml 文件，在其中配置映射端口、持久化目录

1
vim docker-compose.yml

配置文件里的volumes参数路径要修改，不要是/mnt/shared目录就好。

1
version: '3.5'
2

3
services:
4
  db:
5
    image: mariadb:10.6
6
    restart: always
7
    command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW
8
    volumes:
9
      - "/root/kodbox/db:/var/lib/mysql"       #./db是数据库持久化目录，可以修改
10
      # - "./etc/mysql/conf.d:/etc/mysql/conf.d"       #增加自定义mysql配置
11
    environment:
12
      - MYSQL_ROOT_PASSWORD=test@123
13
      - MARIADB_AUTO_UPGRADE=1
14
      - MARIADB_DISABLE_UPGRADE_BACKUP=1
15
    env_file:
16
      - db.env
17

18
  app:
19
    image: kodcloud/kodbox
20
    restart: always
21
    ports:
22
      - 8088:80                       #左边8088是使用端口，可以修改
23
    volumes:
24
      - "/root/kodbox/site:/var/www/html"      #./site是站点目录位置，可以修改
25
    environment:
26
      - MYSQL_HOST=db
27
      - REDIS_HOST=redis
28
    env_file:
29
      - db.env
30
    depends_on:
31
      - db
32
      - redis
33

34
  redis:
35
    image: redis:alpine
36
    restart: always

增加自定义mysql配置，在/root/kodbox目录下

1
mkdir -p ./etc/mysql/conf.d && vim ./etc/mysql/conf.d/custom.cnf

好了！万事俱备只欠东风，现在可以运行容器了，在/root/kodbox目录下执行docker-compose命令

1
root@alpine-term ~/kodbox # docker-compose up -d
2
[+] Running 3/3
3
 ✔ Container kodbox-redis-1  Started
4
 ✔ Container kodbox-db-1     Started
5
 ✔ Container kodbox-app-1    Started

容器启动成功后，查看容器的运行状态，一切正常。

1
root@alpine-term ~/kodbox # docker ps
2
CONTAINER ID   IMAGE             COMMAND                  CREATED         STATUS              PORTS                                     NAMES
3
eb836231f104   kodcloud/kodbox   "/entrypoint.sh supe…"   5 minutes ago   Up About a minute   443/tcp, 9000/tcp, 0.0.0.0:8088->80/tcp   kodbox-app-1
4
7eae29c2919e   redis:alpine      "docker-entrypoint.s…"   5 minutes ago   Up 3 minutes        6379/tcp                                  kodbox-redis-1
5
ef60633e2ead   mariadb:10.6      "docker-entrypoint.s…"   5 minutes ago   Up 3 minutes        3306/tcp                                  kodbox-db-1

但是此时还不能确定真的一切正常，我们需要确定之前的因目录权限问题导致的mariadb数据库容器报错find: ‘/var/lib/mysql/’: Operation not permitted的问题还有没有！

查看mariadb数据库容器日志

1
docker logs -f --tail 500 ef60633e2ead

日志

1
db-1  | 2024-05-11 04:58:10+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.17+maria~ubu2004 started.
2
db-1  | 2024-05-11 04:58:15+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
3
db-1  | 2024-05-11 04:58:15+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.6.17+maria~ubu2004 started.
4
db-1  | 2024-05-11 04:58:19+00:00 [Note] [Entrypoint]: Initializing database files
5
db-1  |
6
db-1  |
7
db-1  | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
8
db-1  | To do so, start the server, then issue the following command:
9
db-1  |
10
db-1  | '/usr/bin/mariadb-secure-installation'
11
db-1  |
12
db-1  | which will also give you the option of removing the test
13
db-1  | databases and anonymous user created by default.  This is
14
db-1  | strongly recommended for production servers.
15
db-1  |
16
db-1  | See the MariaDB Knowledgebase at https://mariadb.com/kb
17
db-1  |
18
db-1  | Please report any problems at https://mariadb.org/jira
19
db-1  |
20
db-1  | The latest information about MariaDB is available at https://mariadb.org/.
21
db-1  |
22
db-1  | Consider joining MariaDB's strong and vibrant community:
23
db-1  | https://mariadb.org/get-involved/
24
db-1  |
25
db-1  | 2024-05-11 04:58:43+00:00 [Note] [Entrypoint]: Database files initialized
26
db-1  | 2024-05-11 04:58:43+00:00 [Note] [Entrypoint]: Starting temporary server
27
db-1  | 2024-05-11 04:58:43+00:00 [Note] [Entrypoint]: Waiting for server startup
28
db-1  | 2024-05-11  4:58:44 0 [Note] Starting MariaDB 10.6.17-MariaDB-1:10.6.17+maria~ubu2004-log source revision 15c75ad083a55e198ae78324f22970694b72f22b as process 95
29
db-1  | 2024-05-11  4:58:45 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
30
db-1  | 2024-05-11  4:58:45 0 [Note] InnoDB: Number of pools: 1
31
db-1  | 2024-05-11  4:58:45 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
32
db-1  | 2024-05-11  4:58:45 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
33
db-1  | 2024-05-11  4:58:45 0 [Note] InnoDB: Using Linux native AIO
34
db-1  | 2024-05-11  4:58:45 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
35
db-1  | 2024-05-11  4:58:45 0 [Note] InnoDB: Completed initialization of buffer pool
36
db-1  | 2024-05-11  4:58:46 0 [Note] InnoDB: 128 rollback segments are active.
37
db-1  | 2024-05-11  4:58:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
38
db-1  | 2024-05-11  4:58:46 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
39
db-1  | 2024-05-11  4:58:46 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
40
db-1  | 2024-05-11  4:58:46 0 [Note] InnoDB: 10.6.17 started; log sequence number 42486; transaction id 14
41
db-1  | 2024-05-11  4:58:46 0 [Note] Plugin 'FEEDBACK' is disabled.
42
db-1  | 2024-05-11  4:58:46 0 [Warning] 'user' entry 'root@46f814c57da6' ignored in --skip-name-resolve mode.
43
db-1  | 2024-05-11  4:58:47 0 [Warning] 'proxies_priv' entry '@% root@46f814c57da6' ignored in --skip-name-resolve mode.
44
db-1  | 2024-05-11  4:58:47 0 [Note] mariadbd: ready for connections.
45
db-1  | Version: '10.6.17-MariaDB-1:10.6.17+maria~ubu2004-log'  socket: '/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
46
db-1  | 2024-05-11 04:58:47+00:00 [Note] [Entrypoint]: Temporary server started.
47
db-1  | 2024-05-11 05:00:21+00:00 [Note] [Entrypoint]: Creating database kodbox
48
db-1  | 2024-05-11 05:00:21+00:00 [Note] [Entrypoint]: Creating user kodbox
49
db-1  | 2024-05-11 05:00:21+00:00 [Note] [Entrypoint]: Giving user kodbox access to schema kodbox
50
db-1  | 2024-05-11 05:00:21+00:00 [Note] [Entrypoint]: Securing system users (equivalent to running mysql_secure_installation)
51
db-1  |
52
db-1  | 2024-05-11 05:00:22+00:00 [Note] [Entrypoint]: Stopping temporary server
53
db-1  | 2024-05-11  5:00:22 0 [Note] mariadbd (initiated by: unknown): Normal shutdown
54
db-1  | 2024-05-11  5:00:22 0 [Note] InnoDB: FTS optimize thread exiting.
55
db-1  | 2024-05-11  5:00:23 0 [Note] InnoDB: Starting shutdown...
56
db-1  | 2024-05-11  5:00:23 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
57
db-1  | 2024-05-11  5:00:23 0 [Note] InnoDB: Buffer pool(s) dump completed at 240511  5:00:23
58
db-1  | 2024-05-11  5:00:23 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
59
db-1  | 2024-05-11  5:00:23 0 [Note] InnoDB: Shutdown completed; log sequence number 42514; transaction id 15
60
db-1  | 2024-05-11  5:00:23 0 [Note] mariadbd: Shutdown complete
61
db-1  |
62
db-1  | 2024-05-11 05:00:23+00:00 [Note] [Entrypoint]: Temporary server stopped
63
db-1  |
64
db-1  | 2024-05-11 05:00:23+00:00 [Note] [Entrypoint]: MariaDB init process done. Ready for start up.
65
db-1  |
66
db-1  | 2024-05-11  5:00:24 0 [Note] Starting MariaDB 10.6.17-MariaDB-1:10.6.17+maria~ubu2004-log source revision 15c75ad083a55e198ae78324f22970694b72f22b as process 1
67
db-1  | 2024-05-11  5:00:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
68
db-1  | 2024-05-11  5:00:25 0 [Note] InnoDB: Number of pools: 1
69
db-1  | 2024-05-11  5:00:25 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
70
db-1  | 2024-05-11  5:00:25 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
71
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: Using Linux native AIO
72
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
73
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: Completed initialization of buffer pool
74
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: 128 rollback segments are active.
75
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables
76
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
77
db-1  | 2024-05-11  5:00:26 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
78
db-1  | 2024-05-11  5:00:27 0 [Note] InnoDB: 10.6.17 started; log sequence number 42514; transaction id 14
79
db-1  | 2024-05-11  5:00:27 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
80
db-1  | 2024-05-11  5:00:27 0 [Note] Plugin 'FEEDBACK' is disabled.
81
db-1  | 2024-05-11  5:00:27 0 [Note] InnoDB: Buffer pool(s) load completed at 240511  5:00:27
82
db-1  | 2024-05-11  5:00:27 0 [Note] Server socket created on IP: '0.0.0.0'.
83
db-1  | 2024-05-11  5:00:27 0 [Note] Server socket created on IP: '::'.

容器正常了！

3、端口映射

正常来说此时可以通过http://IP:8088访问页面。但是由于Alpine-termux是termux中的虚拟机，所以现在和之前映射22端口的逻辑是一致的，想在局域网其它电脑访问，还需要一步端口映射的步骤。

手指在Alpine-termux APP软件的左上方向右滑动，调出菜单。

选择[1]QEMU，映射docker-compose.yml文件中的8088端口到手机的8088端口，

输入

1
hostfwd_add tcp::8088-:8088

无报错即映射成功。确保手机和电脑端在同一局域网，在电脑上访问手机IP+8088端口：http://172.16.12.21:8088 即可进入可道云盘系统页面。

4、注意事项

使用df -h命令查看Alpine-termux虚拟机磁盘使用情况：

1
df -h

这里看见/mnt/shared 的容量是最大的。但是这个问题前面也说了，因为/mnt/shared是手机目录的原因，所以我们在这个目录下的操作有些寸步难行，因为权限问题嘛。也导致虽然云盘部署完成了，但是其它目录太小，数据库也会有持久化，没有足够空间存放资料的难题。所以这个问题，需要我们在手机上新增一张sd存储卡。或者使用OTG外接硬盘，但是这个也具体看手机是否支持，这个可以咨询手机官方。外接存储方案实现后，需在Alpine-termux虚拟机里将外接的磁盘挂载到Alpine-termux虚拟机系统。

全篇完！

参考链接#

————————————————

1
                        版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

原文链接：https://blog.csdn.net/AnRanGeSi/article/details/138717589

音乐

音乐