Após atualização do Docker wppserver (2.2.5), criação do container resultou em 'prom-client'

[rafaeldimauro]

Description:

Após atualização do Docker wppserver (2.2.5), criação do container resultou em 'prom-client'

Environment:
CentOS Stream release 9
NAME="CentOS Stream"
VERSION="9"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="9"
PLATFORM_ID="platform:el9"
PRETTY_NAME="CentOS Stream 9"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:centos:centos:9"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"
CentOS Stream release 9

Steps to Reproduce

Após instalação:
docker run -p 8080:8080 --name server-cli --rm wppconnect/server-cli:latest wppserver --secretKey {secretkey} --port 8080 --frontend

o erro de prom-client foi apresentado:

ao acessar as pastas dos containers criados em (/var/lib/docker/overlay2/), executei um find (find . | grep "server-cli") para encontrar as pastas da aplicação.
Entrei pasta a pasta e executei o npm -i force para instalação dos pacotes.
O erro de prom-client resolveu, porém, ao executar o container, qualquer comando "crasha" e finaliza a execução.

Log Output

Não encontrei log relativo ao erro. Apenas a consequencia de crash em /var/log/messages:

Aug 31 14:37:37 SUPPER-DOCKER01 kernel: node[43422]: segfault at 4190 ip 0000000000004190 sp 00007f84b75a7708 error 14 likely on CPU 3 (core 0, socket 6)
Aug 31 14:37:37 SUPPER-DOCKER01 kernel: Code: Unable to access opcode bytes at RIP 0x4166.
Aug 31 14:37:37 SUPPER-DOCKER01 systemd[1]: Started Process Core Dump (PID 43424/UID 0).
Aug 31 14:37:38 SUPPER-DOCKER01 [43426]: Could not parse number of program headers from core file: invalid Elf' handle Aug 31 14:37:38 SUPPER-DOCKER01 [43426]: Could not parse number of program headers from core file: invalid Elf' handle
Aug 31 14:37:38 SUPPER-DOCKER01 [43426]: Could not parse number of program headers from core file: invalid Elf' handle Aug 31 14:37:38 SUPPER-DOCKER01 [43426]: Could not parse number of program headers from core file: invalid Elf' handle
Aug 31 14:37:38 SUPPER-DOCKER01 [43426]: Could not parse number of program headers from core file: invalid Elf' handle Aug 31 14:37:38 SUPPER-DOCKER01 [43426]: Could not parse number of program headers from core file: invalid Elf' handle
Aug 31 14:37:38 SUPPER-DOCKER01 systemd-coredump[43425]: Process 43394 (node) of user 0 dumped core.#12#012Module /usr/local/bin/node without build-id.#012Module /usr/local/bin/node#012Module /usr/src/server-cli/node_modules/sharp/vendor/8.14.4/linuxmusl-x64/lib/libvips-cpp.so.42 without build-id.#012Module /usr/src/server-cli/node_modules/sharp/vendor/8.14.4/linuxmusl-x64/lib/libvips-cpp.so.42#012Module /usr/src/server-cli/node_modules/sharp/build/Release/sharp-linuxmusl-x64.node without build-id.#012Module /usr/src/server-cli/node_modules/sharp/build/Release/sharp-linuxmusl-x64.node#012Module /usr/lib/libgcc_s.so.1 without build-id.#012Module /usr/lib/libgcc_s.so.1#012Module /usr/lib/libstdc++.so.6.0.30 without build-id.#012Module /usr/lib/libstdc++.so.6.0.30#012Module /lib/ld-musl-x86_64.so.1 without build-id.#012Module /lib/ld-musl-x86_64.so.1#012Stack trace of thread 15:#12#0 0x0000000000004190 n/a (n/a + 0x0)#12#1 0x00007f84b98eb9d8 n/a (/usr/src/server-cli/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node + 0xd9d8)#12#2 0x000056404c5235c9 n/a (/usr/local/bin/node + 0x13a05c9)#12#3 0x00007f84c5d2cbd2 n/a (/lib/ld-musl-x86_64.so.1 + 0x55bd2)#012ELF object binary architecture: AMD x86-64
Aug 31 14:37:38 SUPPER-DOCKER01 systemd[1]: systemd-coredump@15-43424-0.service: Deactivated successfully.
Aug 31 14:37:38 SUPPER-DOCKER01 systemd[1]: docker-9da1998b66443d61d3074c243b8a6a7fb530e05f09b583a076b7ad1f681564d3.scope: Deactivated successfully.
Aug 31 14:37:38 SUPPER-DOCKER01 systemd[1]: docker-9da1998b66443d61d3074c243b8a6a7fb530e05f09b583a076b7ad1f681564d3.scope: Consumed 1.610s CPU time.
Aug 31 14:37:38 SUPPER-DOCKER01 dockerd[39222]: time="2023-08-31T14:37:38.511456856-03:00" level=info msg="ignoring event" container=9da1998b66443d61d3074c243b8a6a7fb530e05f09b583a076b7ad1f681564d3 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Aug 31 14:37:38 SUPPER-DOCKER01 containerd[869]: time="2023-08-31T14:37:38.511551237-03:00" level=info msg="shim disconnected" id=9da1998b66443d61d3074c243b8a6a7fb530e05f09b583a076b7ad1f681564d3
Aug 31 14:37:38 SUPPER-DOCKER01 containerd[869]: time="2023-08-31T14:37:38.511664450-03:00" level=warning msg="cleaning up after shim disconnected" id=9da1998b66443d61d3074c243b8a6a7fb530e05f09b583a076b7ad1f681564d3 namespace=moby
Aug 31 14:37:38 SUPPER-DOCKER01 containerd[869]: time="2023-08-31T14:37:38.511673764-03:00" level=info msg="cleaning up dead shim"
Aug 31 14:37:38 SUPPER-DOCKER01 containerd[869]: time="2023-08-31T14:37:38.518554021-03:00" level=warning msg="cleanup warnings time="2023-08-31T14:37:38-03:00" level=info msg="starting signal loop" namespace=moby pid=43436 runtime=io.containerd.runc.v2\n"
Aug 31 14:37:38 SUPPER-DOCKER01 kernel: docker0: port 1(veth12f4ce6) entered disabled state
Aug 31 14:37:38 SUPPER-DOCKER01 kernel: vethca52433: renamed from eth0
Aug 31 14:37:38 SUPPER-DOCKER01 NetworkManager[838]: [1693503458.5796] manager: (vethca52433): new Veth device (/org/freedesktop/NetworkManager/Devices/123)
Aug 31 14:37:38 SUPPER-DOCKER01 kernel: docker0: port 1(veth12f4ce6) entered disabled state
Aug 31 14:37:38 SUPPER-DOCKER01 kernel: device veth12f4ce6 left promiscuous mode
Aug 31 14:37:38 SUPPER-DOCKER01 kernel: docker0: port 1(veth12f4ce6) entered disabled state
Aug 31 14:37:38 SUPPER-DOCKER01 systemd[1]: run-docker-netns-bb988a61fc94.mount: Deactivated successfully.
Aug 31 14:37:38 SUPPER-DOCKER01 systemd[1]: var-lib-docker-overlay2-124c6e19f4e3c0be38cbd74f509051912ac804cbade336b5e59388df6b08e947-merged.mount: Deactivated successfully.

[renat473]

#466