堆棧內存溢出
  簡體   English   中英

使用 Paketo Buildpacks 容器化 Angular 應用程序：空回復

[英]Containerizing Angular Application With Paketo Buildpacks: Empty Reply

 原文  2021-08-13 10:19:22  4   2    node.js/ angular/ buildpack/ paketo

問題描述

我想使用適用於 nodejs 的 Paketo buildpack 創建我的 Angular 12 應用程序的容器映像。 我通過 Angular CLI 創建了應用程序並將其編碼，直到現在我想部署它。

為了創建容器，我按照 paketo 示例存儲庫中的說明運行了以下命令：

pack build myui --buildpack gcr.io/paketo-buildpacks/nodejs --env "BP_NODE_RUN_SCRIPTS=build" --env "NODE_ENV=development"

這很好用，因為我在運行pack之前刪除了 node_modules 目錄。

現在我想在本地測試圖像並嘗試使用

docker run --tty --publish 4200:4200 myui

好像啟動成功了：

✔ Browser application bundle generation complete.

Initial Chunk Files | Names         |      Size
main.js             | main          |   6.14 MB
vendor.js           | vendor        |   4.22 MB
styles.css          | styles        | 159.33 kB
polyfills.js        | polyfills     | 128.67 kB
runtime.js          | runtime       |   6.56 kB

                    | Initial Total |  10.65 MB

Build at: 2021-08-13T10:06:14.282Z - Hash: 5351646d56eaa8873a38 - Time: 15305ms

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **


✔ Compiled successfully.
✔ Browser application bundle generation complete.

5 unchanged chunks

Build at: 2021-08-13T10:06:15.412Z - Hash: 149b56c677aa74ba2361 - Time: 577ms

✔ Compiled successfully.

現在問題來了：

➜  ~ docker ps
CONTAINER ID   IMAGE     COMMAND              CREATED          STATUS          PORTS                                       NAMES
6a29ce4cdc86   myui      "/cnb/process/web"   11 minutes ago   Up 11 minutes   0.0.0.0:4200->4200/tcp, :::4200->4200/tcp   confident_grothendieck
➜  ~ curl -vvv http://localhost:4200/
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 4200 (#0)
> GET / HTTP/1.1
> Host: localhost:4200
> User-Agent: curl/7.64.1
> Accept: */*
>
* Empty reply from server
* Connection #0 to host localhost left intact
curl: (52) Empty reply from server
* Closing connection 0
➜  ~

有誰知道出了什么問題？

編輯：我目前最好的猜測是ng serve監聽 127.0.0.1:4200 但應該監聽0.0.0.0:4200以讓流量通過。 但我不確定在哪里尋找配置。 在構建包中？ 在 angular.cli 中？ 別的地方？

編輯：根據要求， pack命令的完整輸出：

➜  ui2 git:(master) pack build myui --buildpack gcr.io/paketo-buildpacks/nodejs --env "BP_NODE_RUN_SCRIPTS=build" --env "NODE_ENV=development"
full: Pulling from paketobuildpacks/builder
Digest: sha256:b34eb3b43d6bf20623ad92523e9e1a055289e74a2fa661adee5d1d90e25afd48
Status: Image is up to date for paketobuildpacks/builder:full
full-cnb: Pulling from paketobuildpacks/run
Digest: sha256:691eb052281456ab5b5a62d1a0e5a67bf7246783565bbecd239c5c9cf1bf51ec
Status: Image is up to date for paketobuildpacks/run:full-cnb
latest: Pulling from paketo-buildpacks/nodejs
Digest: sha256:9887bb6b7d0c410ccdf6fa940658dddecfce5ded1ac5696ced608c78649594b3
Status: Image is up to date for gcr.io/paketo-buildpacks/nodejs:latest
===> DETECTING
5 of 8 buildpacks participating
paketo-buildpacks/ca-certificates 2.3.2
paketo-buildpacks/node-engine     0.6.2
paketo-buildpacks/npm-install     0.4.0
paketo-buildpacks/node-run-script 0.1.0
paketo-buildpacks/npm-start       0.3.0
===> ANALYZING
Previous image with name "myui" not found
===> RESTORING
===> BUILDING

Paketo CA Certificates Buildpack 2.3.2
  https://github.com/paketo-buildpacks/ca-certificates
  Launch Helper: Contributing to layer
    Creating /layers/paketo-buildpacks_ca-certificates/helper/exec.d/ca-certificates-helper
Paketo Node Engine Buildpack 0.6.2
  Resolving Node Engine version
    Candidate version sources (in priority order):
                -> ""
      <unknown> -> ""

    Selected Node Engine version (using ): 14.17.5

  Executing build process
    Installing Node Engine 14.17.5
      Completed in 7.96s

  Configuring build environment
    NODE_ENV     -> "development"
    NODE_HOME    -> "/layers/paketo-buildpacks_node-engine/node"
    NODE_VERBOSE -> "false"

  Configuring launch environment
    NODE_ENV     -> "production"
    NODE_HOME    -> "/layers/paketo-buildpacks_node-engine/node"
    NODE_VERBOSE -> "false"

    Writing profile.d/0_memory_available.sh
      Calculates available memory based on container limits at launch time.
      Made available in the MEMORY_AVAILABLE environment variable.

Paketo NPM Install Buildpack 0.4.0
  Resolving installation process
    Process inputs:
      node_modules      -> "Not found"
      npm-cache         -> "Not found"
      package-lock.json -> "Found"

    Selected NPM build process: 'npm ci'

  Executing build process
    Running 'npm ci --unsafe-perm --cache /layers/paketo-buildpacks_npm-install/npm-cache'
      Completed in 23.58s

  Configuring launch environment
    NPM_CONFIG_LOGLEVEL -> "error"

  Configuring environment shared by build and launch
    PATH -> "$PATH:/layers/paketo-buildpacks_npm-install/modules/node_modules/.bin"


Paketo Node Run Script Buildpack 0.1.0
  Executing build process
    Executing scripts
      Running 'npm run-script build'

        > edit@0.0.0 build /workspace
        > ng build

        - Generating browser application bundles (phase: setup)...
        Compiling @angular/core : es2015 as esm2015
        Compiling @angular/cdk/keycodes : es2015 as esm2015
        Compiling @angular/animations : es2015 as esm2015
        Compiling @angular/animations/browser : es2015 as esm2015
        Compiling @angular/cdk/observers : es2015 as esm2015
        Compiling @angular/common : es2015 as esm2015
        Compiling @angular/cdk/collections : es2015 as esm2015
        Compiling @angular/platform-browser : es2015 as esm2015
        Compiling @angular/cdk/platform : es2015 as esm2015
        Compiling @angular/cdk/bidi : es2015 as esm2015
        Compiling @angular/platform-browser/animations : es2015 as esm2015
        Compiling @angular/cdk/a11y : es2015 as esm2015
        Compiling @angular/forms : es2015 as esm2015
        Compiling @angular/flex-layout/core : es2015 as esm2015
        Compiling @angular/cdk/scrolling : es2015 as esm2015
        Compiling @angular/cdk/portal : es2015 as esm2015
        Compiling @angular/cdk/layout : es2015 as esm2015
        Compiling @angular/material/core : es2015 as esm2015
        Compiling @angular/common/http : es2015 as esm2015
        Compiling @angular/cdk/overlay : es2015 as esm2015
        Compiling @angular/flex-layout/extended : es2015 as esm2015
        Compiling @angular/material/button : es2015 as esm2015
        Compiling @angular/flex-layout/flex : es2015 as esm2015
        Compiling @angular/flex-layout/grid : es2015 as esm2015
        Compiling @angular/platform-browser-dynamic : es2015 as esm2015
        Compiling @angular/router : es2015 as esm2015
        Compiling @angular/material/sidenav : es2015 as esm2015
        Compiling @angular/material/snack-bar : es2015 as esm2015
        Compiling @angular/material/toolbar : es2015 as esm2015
        Compiling @angular/material/icon : es2015 as esm2015
        Compiling @angular/flex-layout : es2015 as esm2015
        Compiling @angular/material/tabs : es2015 as esm2015
        ✔ Browser application bundle generation complete.
        ✔ Browser application bundle generation complete.
        - Copying assets...
        ✔ Copying assets complete.
        - Generating index html...
        ✔ Index html generation complete.

        Initial Chunk Files               | Names         |       Size
        main.a6760a1641b4d1eaecd4.js      | main          |    4.50 MB
        styles.8a29e51b15a5b6e5b823.css   | styles        |   90.06 kB
        polyfills.a6c44b054b34d2bec03f.js | polyfills     |   35.96 kB
        runtime.543bd02f52b0afc6ba6a.js   | runtime       | 1015 bytes

        | Initial Total |    4.63 MB

        Build at: 2021-08-16T15:19:15.350Z - Hash: 0958e10b7d5232954d2e - Time: 46738ms

        ./src/app/footer/footer.component.scss - Warning: Module Warning (from ../layers/paketo-buildpacks_npm-install/modules/node_modules/postcss-loader/dist/cjs.js):
        Warning

        (7:3) postcss-preset-env: start value has mixed support, consider using flex-start instead

        ./src/app/home/home.component.scss - Warning: Module Warning (from ../layers/paketo-buildpacks_npm-install/modules/node_modules/postcss-loader/dist/cjs.js):
        Warning

        (84:3) postcss-preset-env: start value has mixed support, consider using flex-start instead

        ./src/app/home/home.component.scss - Warning: Module Warning (from ../layers/paketo-buildpacks_npm-install/modules/node_modules/postcss-loader/dist/cjs.js):
        Warning

        (85:3) postcss-preset-env: start value has mixed support, consider using flex-start instead

        Warning: /workspace/src/app/resize.service.ts depends on 'element-resize-detector'. CommonJS or AMD dependencies can cause optimization bailouts.
        For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies

        Warning: initial exceeded maximum budget. Budget 500.00 kB was not met by 4.14 MB with a total of 4.63 MB.



      Completed in 51.831s

Paketo NPM Start Buildpack 0.3.0
  Assigning launch processes
    web: ng serve

===> EXPORTING
Adding layer 'paketo-buildpacks/ca-certificates:helper'
Adding layer 'paketo-buildpacks/node-engine:node'
Adding layer 'paketo-buildpacks/npm-install:modules'
Adding layer 'paketo-buildpacks/npm-install:npm-cache'
Adding 1/1 app layer(s)
Adding layer 'launcher'
Adding layer 'config'
Adding layer 'process-types'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label 'io.buildpacks.build.metadata'
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'web'
Saving myui...
*** Images (b9cd591df4be):
      myui
Adding cache layer 'paketo-buildpacks/node-engine:node'
Adding cache layer 'paketo-buildpacks/npm-install:modules'
Adding cache layer 'paketo-buildpacks/npm-install:npm-cache'
Successfully built image myui

2 個解決方案

解決方案1
 2  2021-08-16 19:10:21

舊答案

這是舊答案。 僅將其留給歷史背景。 請改用@Frankie Gallina-Jones 的答案。

我會在我的答案前面說，有多種方法可以做到這一點。 以下是我建議的兩種方法：

本地構建

  1. 在本地構建，比如在你的機器上運行npm build 。

  2. 添加一個buildpack.yml文件：

     staticfile: nginx: pushstate: true

    這將指示靜態文件 buildpack 生成支持 pushstate 的 Nginx 配置，這是單頁 Javascript 應用程序通常需要的。

  3. 運行pack build myui -b paketo-buildpacks/nginx -b paketo-community/staticfile -p dist/。 其中dist/是第 1 步構建過程輸出的路徑（即靜態 HTML/CSS/Javascript 所在的位置）。

    確保您的dist/路徑包含您在上一步中創建的buildpack.yml文件。 這是靜態文件構建包通過檢測所必需的。 如果您在嘗試構建時看到No buildpack groups passed detection ，這可能就是原因。

  4. 然后你可以執行docker run -d -e PORT=8080 -p 8080:8080 myui它會運行你的鏡像。 生成的 nginx.conf 期望將PORT設置為您希望它偵聽的某個端口。 只需確保您選擇的端口與參數-p匹配，因此 docker 會公開相同的端口。

本地構建的優勢在於它簡單且適用於大多數應用程序，因為構建的輸出只是靜態 HTML/CSS/JS 和其他資產文件。 buildpack 只是添加了 Nginx，你就可以參加比賽了。

構建包構建

  1. 添加一個buildpack.yml文件：

     staticfile: nginx: pushstate: true

    這將指示靜態文件 buildpack 生成支持 pushstate 的 Nginx 配置，這是單頁 Javascript 應用程序通常需要的。

    確保您創建的buildpack.yml文件位於項目的根目錄下，即您在下一步中運行pack build的目錄。 這是靜態文件構建包通過檢測所必需的。 如果您在嘗試構建時看到No buildpack groups passed detection ，這可能就是原因。

  2. 運行pack build myui -b paketo-buildpacks/nodejs --env "BP_NODE_RUN_SCRIPTS=build" --env "NODE_ENV=development" --buildpack paketo-buildpacks/nginx --buildpack paketo-community/staticfile

這將確保安裝了 Node 和 NPM，然后它將運行npm build 。 這將從您的應用程序中生成靜態文件資源。 然后 Nginx 和 staticfile buildpack 將運行以安裝和配置 Nginx 以托管您的應用程序的靜態文件。

它類似於本地構建，但不需要您在本地安裝 Node 或 NPM。 buildpacks 將安裝它們並在容器內構建。

我建議這兩個構建過程之一的原因是因為任何一個都會導致啟動容器很小並且只包含您的靜態文件和 Nginx。 與使用構建工具的開發服務器安裝 Node.js 相比，這將更小、更高效、更適合生產。

解決方案2
 2 已采納  2022-06-13 14:30:19

Paketo 現在有一個為這樣的用例設計的 Web 服務器構建包。 有關使用 buildpack 將 Angular、React、Vue.js 或其他前端框架應用程序容器化的步驟，請參閱 Paketo 文檔。

您可能需要的pack build命令是：

pack build myui -b paketo-buildpacks/web-servers \
--env "BP_WEB_SERVER=nginx" \
--env "BP_WEB_SERVER_ROOT=dist" \
--env "BP_WEB_SERVER_ENABLE_PUSH_STATE=true" \
--env "NODE_ENV=development"

這將：

  • 設置 buildpack 以提供在構建期間編譯到dist目錄中的靜態資產
  • 自動生成啟用推送狀態路由的 nginx.conf ，單頁應用程序可能需要它
  • 自動生成一個精簡的 Docker 映像，其中不包含您龐大的node_modules

暫無
暫無

聲明:本站的技術帖子網頁，遵循CC BY-SA 4.0協議，如果您需要轉載，請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

相關問題 在 Paketo.io / 雲原生 Buildpacks 構建的 Docker 容器中運行 Nuxt.js 來自服務器的nod​​e.js空回復 如何從 API {} 捕獲空回復 接收 cURL 錯誤：來自服務器的空回復 Docker 映像中的 Heroku 構建包 Ubuntu + Nodejs + curl：（52）來自服務器的空回復 Heroku持久$ PATH與muliple buildpacks Angular中的NodeJS空返回 “本地主機沒有發送數據。 ERR_EMPTY_RESPONSE”和“curl: (52) 來自服務器的空回復” 使用Hapi和Async的API - 如何在“回復”之后或每次新的“獲取”時清空數組/執行某些操作？
相關標簽
 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM