Next.js?Docker鏡像私有部署從零實(shí)現(xiàn)
預(yù)備
經(jīng)過一周的零碎開發(fā),大致完成了雛形。簡(jiǎn)單完成了文件移動(dòng)、文件刪除、圖片預(yù)覽、視頻播放??紤]部署一版看看效果。
- 自建 docker registry 私有倉(cāng)庫(kù)儲(chǔ)存構(gòu)建好的鏡像
- 創(chuàng)建 Dockerfile,開發(fā)機(jī)器構(gòu)建好鏡像后上傳至私有 docker 鏡像倉(cāng)庫(kù)
- NAS 使用 Docker Compose 啟動(dòng)容器。通過私有 docker registry 倉(cāng)庫(kù)獲取鏡像運(yùn)行
package.json 新增下面 scripts
"scripts": {
"explorer-dev": "npm run -w explorer dev",
"explorer-build": "npm run -w explorer build",
"explorer-start": "npm run -w explorer start",
"explorer-check-types": "npm run -w explorer check-types",
"explorer-build-docker": "docker build -f explorer.full.Dockerfile -t 192.168.31.17:5000/tool-manager/explorer .",
"explorer-push-docker": "docker push 192.168.31.17:5000/tool-manager/explorer"
}/explorer 新增依賴
pnpm i sharp
用于加速 Image 縮略圖的生成
私有鏡像倉(cāng)庫(kù)
使用官方提供的 registry 鏡像
docker run -d -p 5000:5000 --restart always --name registry registry:2
需要注意,這里沒有配置鏡像卷目錄,重建容器時(shí)之前上傳的鏡像與配置會(huì)丟失。
主要是下面兩個(gè)
- /var/lib/registry:存放鏡像目錄地址
- /etc/docker/registry/:存放配置文件地址
配置 registry
由于 docker push/pull 需要使用 https。非 https 將會(huì)提示失敗??赏ㄟ^配置 insecure-registries 繞過 https 檢測(cè)。
docker desktop
進(jìn)入設(shè)置頁(yè),Docker Engine 菜單,添加
{
...
"insecure-registries": [
"192.168.31.17:5000"
]
}docker
vim /etc/docker/daemon.json
{
"insecure-registries" : ["192.168.31.17:5000"]
}或者在啟動(dòng) docker 服務(wù)的時(shí)候加上參數(shù)
--insecure-registry 192.168.31.17:5000
構(gòu)建 Docker
Dockerfile
使用的官方構(gòu)建的例子 參考鏈接 進(jìn)行特定修改,新增了
- 阿里的 alpine 源,加速 apk 的安裝
- 配置 npm 加速源
流程
- 使用 20.9.0-alpine 的 node 鏡像作為基礎(chǔ)(base)鏡像,并安裝 libc6-compat 庫(kù)。讓后續(xù)使用 base 鏡像的都擁有 libc6-compat 庫(kù)
- 在(deps)鏡像內(nèi),將 package.json 復(fù)制到對(duì)應(yīng)目錄,并執(zhí)行依賴初始化安裝
- 將初始化好的依賴復(fù)制值運(yùn)行打包(builder)鏡像內(nèi),執(zhí)行 Next.js 編譯
- 將 Next.js 編譯好的文件復(fù)制至運(yùn)行(runner)鏡像內(nèi)。完成整體的創(chuàng)建鏡像流程
FROM node:20.9.0-alpine AS base # 添加源 RUN sed -i 's/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g' /etc/apk/repositories # Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed. RUN apk add --no-cache libc6-compat # Install dependencies only when needed FROM base AS deps WORKDIR /app # Install dependencies based on the preferred package manager COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* pnpm-workspace.yaml* ./ COPY explorer/package.json ./explorer/package.json COPY explorer-manager/package.json ./explorer-manager/package.json RUN npm config set registry https://registry.npmmirror.com/ RUN \ if [ -f yarn.lock ]; then yarn --frozen-lockfile; \ elif [ -f package-lock.json ]; then npm ci; \ elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i --frozen-lockfile; \ else echo "Lockfile not found." && exit 1; \ fi # Rebuild the source code only when needed FROM base AS builder WORKDIR /app COPY --from=deps /app/node_modules ./node_modules COPY --from=deps /app/explorer/node_modules ./explorer/node_modules COPY --from=deps /app/explorer-manager/node_modules ./explorer-manager/node_modules COPY . . # Next.js collects completely anonymous telemetry data about general usage. # Learn more here: https://nextjs.org/telemetry # Uncomment the following line in case you want to disable telemetry during the build. # ENV NEXT_TELEMETRY_DISABLED 1 RUN npm run explorer-build # If using npm comment out above and use below instead # RUN npm run build # Production image, copy all the files and run next FROM base AS runner WORKDIR /app ENV NODE_ENV production # Uncomment the following line in case you want to disable telemetry during runtime. # ENV NEXT_TELEMETRY_DISABLED 1 # Set the correct permission for prerender cache RUN mkdir .next # Automatically leverage output traces to reduce image size # https://nextjs.org/docs/advanced-features/output-file-tracing COPY --from=builder --chown=1000:100 /app/explorer/.next/standalone ./ COPY --from=builder --chown=1000:100 /app/explorer/.next/static ./explorer/.next/static ENV PORT 3000 # set hostname to localhost ENV HOSTNAME "0.0.0.0" CMD ["node", "./explorer/server.js"]
分步構(gòu)建將最大層度的使用 docker 構(gòu)建緩存。加速構(gòu)建鏡像的過程。還能縮小最終生成鏡像大小。
Dockerfile.dockerignore
排除過濾文件。docker 執(zhí)行 build 時(shí),會(huì)自動(dòng)檢索與當(dāng)前 dockerfile 同名的 *.dockerignore 文件作為排除過濾文件。
用于加速 docker build “transferring dockerfile” 過程。如果不設(shè)置,會(huì)將 build 指定的上下文加入轉(zhuǎn)移過程中。如果 node\_modules、.next 文件過多,會(huì)增加 60s+的時(shí)間。
.idea .git **.Dockerfile **.dockerignore **/node_modules **/npm-debug.log **/.next **/README.md **/.env.*
項(xiàng)目?jī)?nèi)使用了 monorepo。所以使用 **. 、**/批量過濾
docker-compose.yml
啟動(dòng)容器模板。172.17.0.1 為本機(jī) docker 服務(wù)的 ip 地址。
這里同時(shí)配置了 tool-manager/explorer 鏡像與 nginx 鏡像。并為 nginx 指定 nginx.conf 配置文件
version: '3'
services:
explorer-app:
container_name: explorer-app
image: 172.17.0.1:5000/tool-manager/explorer:latest
restart: always
environment:
- EXPLORER_PATH=/mnt
- TZ=Asia/Shanghai
volumes:
- /mnt:/mnt
# - explorer-app-files:/app/explorer/
networks:
- share-explorer
user: 1000:100
# Add more containers below (nginx, postgres, etc.)
nginx:
container_name: explorer-app-nginx
image: nginx:latest
environment:
- TZ=Asia/Shanghai
volumes:
- type: bind
source: ./nginx.conf
target: /etc/nginx/nginx.conf
- /mnt:/mnt
# - explorer-app-files:/app/explorer/
depends_on:
- explorer-app
ports:
- '12200:80'
networks:
- share-explorer
networks:
share-explorer:
# external: true
#volumes:
# explorer-app-files:
# external: falsenginx.conf
events {
worker_connections 1000;
}
http {
include /etc/nginx/mime.types;
upstream nextjs_upstream {
server explorer-app:3000;
}
server {
listen 80;
gzip on;
gzip_proxied any;
gzip_comp_level 4;
gzip_types text/css application/javascript image/svg+xml;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
location /_next/static/ {
expires 365d;
# alias /app/explorer/.next/static/;
proxy_pass http://nextjs_upstream;
}
location /static/ {
expires 365d;
alias /mnt/;
}
location / {
proxy_pass http://nextjs_upstream;
}
}
}- 流量由主機(jī)的 12200 端口進(jìn)入 nginx 的 80 端口。
- 通過反向代理至
networks指定的 share-explorer:3000 文件資源管理器服務(wù)的端口 - 設(shè)置 /\_next/static/ 路徑的今天緩存 365 天。
- 查看原圖、視頻資源的 /static/ 路由通過 nginx 反代理,不再進(jìn)入 Next.js 內(nèi)
也可以使用 - explorer-app-files:/app/explorer/ 共享卷的形式共享 Next.js 的運(yùn)行靜態(tài)文件,交給 nginx 進(jìn)行完全代理alias /app/explorer/.next/static/。
但是會(huì)有一個(gè)問題,當(dāng)重新部署服務(wù)時(shí),由于 explorer-app-files 卷已經(jīng)存在,新的內(nèi)容會(huì)不生效,需要手動(dòng)刪除舊的卷,再重新啟動(dòng)容器時(shí)新的改動(dòng)才會(huì)生效。
啟動(dòng)構(gòu)建
開發(fā)機(jī)器執(zhí)行
$ npm run explorer-build-docker > share-explorer@1.0.0 explorer-build-docker > docker build -f explorer.full.Dockerfile -t 192.168.31.17:5000/tool-manager/explorer . [+] Building 111.4s (23/23) FINISHED docker:desktop-linux => [internal] load build definition from explorer.full.Dockerfile 0.0s => => transferring dockerfile: 2.51kB 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [internal] load metadata for docker.io/library/node:20.9.0-alpine 2.7s => [auth] library/node:pull token for registry-1.docker.io 0.0s => CACHED [base 1/3] FROM docker.io/library/node:20.9.0-alpine@sha256:cb2301e2c5fe3165ba2616591efe53b4b6223849ac0871c138f56d5f7ae8be4b 0.0s => [internal] load build context 0.0s => => transferring context: 243.23kB 0.0s => [base 2/3] RUN sed -i 's/dl-cdn.alpinelinux.org/mirrors.aliyun.com/g' /etc/apk/repositories 0.2s => [base 3/3] RUN apk add --no-cache libc6-compat 1.2s => [builder 1/6] WORKDIR /app 0.0s => [runner 2/4] RUN mkdir .next 0.3s => [deps 2/6] COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* pnpm-workspace.yaml* ./ 0.0s => [deps 3/6] COPY explorer/package.json ./explorer/package.json 0.0s => [deps 4/6] COPY explorer-manager/package.json ./explorer-manager/package.json 0.0s => [deps 5/6] RUN npm config set registry https://registry.npmmirror.com/ 1.3s => [deps 6/6] RUN if [ -f yarn.lock ]; then yarn --frozen-lockfile; elif [ -f package-lock.json ]; then npm ci; elif [ -f pnpm-lock.yaml ]; then yarn global add pnpm && pnpm i --frozen-lockfile; else echo "Lockfile not found." && exit 1; fi 14.1s => [builder 2/6] COPY --from=deps /app/node_modules ./node_modules 3.5s => [builder 3/6] COPY --from=deps /app/explorer/node_modules ./explorer/node_modules 0.0s => [builder 4/6] COPY --from=deps /app/explorer-manager/node_modules ./explorer-manager/node_modules 0.0s => [builder 5/6] COPY . . 0.0s => [builder 6/6] RUN npm run explorer-build 84.8s => [runner 3/4] COPY --from=builder --chown=1000:100 /app/explorer/.next/standalone ./ 0.2s => [runner 4/4] COPY --from=builder --chown=1000:100 /app/explorer/.next/static ./explorer/.next/static 0.0s => exporting to image 0.3s => => exporting layers 0.3s => => writing image sha256:cf1f902944d3fcf3e938c8136b781566500b90d9ff79b122c53ecdad035671ef 0.0s => => naming to 192.168.31.17:5000/tool-manager/explorer
Building 111.4s (23/23) FINISHED 差不多兩分鐘時(shí)間完成了鏡像的構(gòu)建。
查看鏡像信息
$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE 192.168.31.17:5000/tool-manager/explorer latest cf1f902944d3 2 minutes ago 161MB
大小為:161MB
推送鏡像
開發(fā)機(jī)器執(zhí)行
$ npm run explorer-push-docker > share-explorer@1.0.0 explorer-push-docker > docker push 192.168.31.17:5000/tool-manager/explorer Using default tag: latest The push refers to repository [192.168.31.17:5000/tool-manager/explorer] 60f05a6e16d5: Pushed eee1f67860e5: Pushed ff64dffbca6a: Pushed fcc511c2a1f1: Pushed e44450d578c0: Pushed b20d27ca648d: Pushed 45956122da26: Layer already exists e0df4b6a3449: Layer already exists 86d11448d6ef: Layer already exists cc2447e1835a: Layer already exists latest: digest: sha256:3b510f7e600e08d8fe7fb2074053a9272385a6d0833ff9e984563d3b1661425b size: 2409
拉取運(yùn)行容器
需要部署的機(jī)器上執(zhí)行
docker-compose -f explorer.docker-compose.yml up -d
常用 docker 命令
查看當(dāng)前 docker 的磁盤占用
$ docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 3 0 364.2MB 364.2MB (100%) Containers 0 0 0B 0B Local Volumes 1 0 0B 0B Build Cache 74 0 4.481GB 4.481GB
刪除構(gòu)建鏡像緩存
$ docker builder prune
構(gòu)建并后臺(tái)啟動(dòng)
$ docker-compose up --build -d
刪除使用狀態(tài)的 volumes
$ docker system prune -a
清除懸空鏡像
$ docker image prune
以上就是Next.js Docker鏡像私有部署從零實(shí)現(xiàn)的詳細(xì)內(nèi)容,更多關(guān)于Next.js Docker鏡像私有部署的資料請(qǐng)關(guān)注腳本之家其它相關(guān)文章!
相關(guān)文章
DockerCE之執(zhí)行docker info出現(xiàn)兩條警告信息及解決方案
這篇文章主要介紹了DockerCE之執(zhí)行docker info出現(xiàn)兩條警告信息及解決方案,具有很好的參考價(jià)值,希望對(duì)大家有所幫助,如有錯(cuò)誤或未考慮完全的地方,望不吝賜教2024-02-02
基于alpine用dockerfile創(chuàng)建的爬蟲Scrapy鏡像的實(shí)現(xiàn)
這篇文章主要介紹了基于alpine用dockerfile創(chuàng)建的爬蟲Scrapy鏡像的實(shí)現(xiàn),小編覺得挺不錯(cuò)的,現(xiàn)在分享給大家,也給大家做個(gè)參考。一起跟隨小編過來看看吧2018-12-12
Docker搭建Jenkins并自動(dòng)化打包部署項(xiàng)目的步驟
本文主要介紹了Docker搭建Jenkins并自動(dòng)化打包部署項(xiàng)目的步驟,文中通過示例代碼介紹的非常詳細(xì),具有一定的參考價(jià)值,感興趣的小伙伴們可以參考一下2022-03-03

