簡體   English   中英

GCP Kube.netes 找不到 Elixir Dockerfile 項目的 libgcc_s

[英]GCP Kubernetes doesn't find libgcc_s for a Elixir Dockerfile project

語境

目前首次在 Google Cloud 和 Kube.netes 上發布 Elixir/Phoenix 應用程序,(我找到了一個教程,我按照教程 => 使用 Google Kube.netes 引擎在容器中運行 Elixir/Phoenix 應用程序),我'我被困在似乎是最后一步的地方:由於一些我還沒有找到修復的錯誤而部署到集群

該應用程序

elixir 應用程序是一個包含兩個 phoenix 應用程序的傘形應用程序,每個都有一個端口(用於管理網站,另一個用於一般網站)和另外三個 elixir 應用程序。

有一個自定義的 docker 用於開發(使用 docker-compose),另一個Dockerfile 用於生產,這是下面的(分為兩部分,我猜第一部分用於圖像構建,第二部分用於 kube.netes) :

# prod.Dockerfile
FROM elixir:alpine

ARG app_name=prod
ARG phoenix_subdir=.
ARG build_env=prod

RUN apk add --no-cache make build-base openssl ncurses-libs libgcc libstdc++

ENV MIX_ENV=${build_env} TERM=xterm

WORKDIR /opt/app
RUN apk update \
  && apk --no-cache --update add nodejs npm \
  && mix local.rebar --force \
  && mix local.hex --force
COPY . .

RUN mix do deps.get, compile
RUN cd apps/admin/assets \
  && npm rebuild node-sass \
  && npm install \
  && ./node_modules/webpack/bin/webpack.js \
  && cd .. \
  && mix phx.digest

RUN cd apps/app/assets \
  && npm rebuild node-sass \
  && npm install \
  && ./node_modules/webpack/bin/webpack.js \
  && cd .. \
  && mix phx.digest
RUN mix release ${app_name} \
  && mv _build/${build_env}/rel/${app_name} /opt/release \
  && mv /opt/release/bin/${app_name} /opt/release/bin/start_server


FROM alpine:latest

RUN apk add make build-base --no-cache openssl ncurses-libs libgcc libstdc++

ARG hello

RUN apk update \
  && apk add --no-cache postgresql-client \
  && apk --no-cache --update add  bash ca-certificates openssl-dev \
  && mkdir -p /usr/local/bin \
  && wget https://dl.google.com/cloudsql/cloud_sql_proxy.linux.amd64 \
  -O /usr/local/bin/cloud_sql_proxy \
  && chmod +x /usr/local/bin/cloud_sql_proxy \
  && mkdir -p /tmp/cloudsql
ENV GCLOUD_PROJECT_ID=${project_id} \
  REPLACE_OS_VARS=true
EXPOSE ${PORT}
EXPOSE 4011
WORKDIR /opt/app
COPY --from=0 /opt/release .
CMD (/usr/local/bin/cloud_sql_proxy \
  -projects=${GCLOUD_PROJECT_ID} -dir=/tmp/cloudsql &); \
  exec /opt/app/bin/start_server start

cloudbuild.yaml

steps:
- name: "gcr.io/cloud-builders/docker"
  args: ["build", "-t", "gcr.io/hello/prod:$_TAG",
       "--build-arg", "project_id=hello", ".",
       "--file=./prod.Dockerfile"]
images: ["gcr.io/hello/prod:$_TAG"]

步驟

(重新)構建圖像

$> gcloud builds submit --substitutions=_TAG=v1 .

然后創建部署

$> kubectl run hello-web --image=gcr.io/${PROJECT_ID}/hello:v1 --port 8080
pod/hello-web created

檢查部署是否順利(劇透:事實並非如此)

$> kubectl get pods
NAME                  READY   STATUS             RESTARTS   AGE
hello-web   0/1     CrashLoopBackOff   1          15s

查看日志

$> kubectl logs {POD-NAME}

其中顯示以下錯誤:

錯誤

2021/08/09 23:49:15 current FDs rlimit set to 1048576, wanted limit is 8500. Nothing to do here.
2021/08/09 23:49:15 gcloud is not in the path and -instances and -projects are empty
Error loading shared library libstdc++.so.6: No such file or directory (needed by /opt/app/erts-12.0.3/bin/beam.smp)
Error loading shared library libgcc_s.so.1: No such file or directory (needed by /opt/app/erts-12.0.3/bin/beam.smp)
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_begin_catch: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt24__throw_out_of_range_fmtPKcz: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _Znwm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt20__throw_length_errorPKc: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_guard_release: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZNKSt8__detail20_Prime_rehash_policy11_M_next_bktEm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __popcountdi2: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt29_Rb_tree_insert_and_rebalancebPSt18_Rb_tree_node_baseS0_RS_: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt17__throw_bad_allocv: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_appendEPKcm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_createERmm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt18_Rb_tree_incrementPKSt18_Rb_tree_node_base: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_end_catch: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_guard_acquire: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZNKSt8__detail20_Prime_rehash_policy14_M_need_rehashEmmm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt19__throw_logic_errorPKc: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZSt18_Rb_tree_decrementPSt18_Rb_tree_node_base: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE7reserveEm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_rethrow: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _Unwind_Resume: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZdlPvm: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
...
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZTVN10__cxxabiv120__si_class_type_infoE: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_pure_virtual: symbol not found
...
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __cxa_pure_virtual: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found
...
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZTVN10__cxxabiv117__class_type_infoE: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: _ZTVN10__cxxabiv121__vmi_class_type_infoE: symbol not found
Error relocating /opt/app/erts-12.0.3/bin/beam.smp: __gxx_personality_v0: symbol not found

我試過什么

雖然我幾乎一無所知,但我還是試着修改了一點Dockerfile,但沒有成功。 我也在谷歌上搜索 libgcc 錯誤,但沒有成功。

就是這樣,因為我沒有其他線索可以看。

那么,有什么建議可以讓它發揮作用嗎?

其他行為

刪除 pod,然后獲取圖像的標簽並清理它

$> kubectl delete pod hello-web
$> gcloud container images list-tags gcr.io/hello/prod
$> gcloud container images delete gcr.io/hello/prod@sha256:...

編輯

編輯 1 (12/08/2021 19:04)

  • 用最新版本更新 Dockerfile
  • 添加另一個動作列表

結果:什么都沒有改變

看來您的問題已經在 Elixir 論壇上提出過:

https://elixirforum.com/t/docker-run-error-loading-shared-library-libstdc-so-6-and-libgcc-s-so-1/40496

看起來您的最終圖像中缺少運行時依賴項。 嘗試將 RUN apk add --no-cache openssl ncurses-libs 更改為 RUN apk add --no-cache openssl ncurses-libs libstdc++。

解決方法是將libstdc++添加到您的安裝行。

論壇帖子中也概述了這樣做的原因:

Beam 具有本機運行時依賴項,並且 OTP 24 添加了 libc 作為運行時依賴項以支持 JIT。 有了這個改變,似乎 bare alpine:3.9 不再帶來所有必需的運行時依賴性。 您需要確保所有這些都存在於應用程序容器中。

祝你好運!

因此,經過數小時的測試和嘗試,我只是改變了策略並專注於圖像版本而不是 Dockerfile。

$> gcloud builds submit --substitutions=_TAG=v1.1 .
$> kubectl run hello-web --image=gcr.io/${PROJECT_ID}/hello:v1.1 --port 8080

我之前沒有更改它,因為我想在構建和應用程序之間保持相同的版本。

我更改的另一件事是cloudbuild.yaml :我刪除了名稱前面的破折號。

這兩個操作使構建在 pod 中運行。

暫無
暫無

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

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM