docker build error

[lgyhit]

I tried build a c++ source file to a wasm module using proxy-wasm-cpp-sdk (https://github.com/proxy-wasm/proxy-wasm-cpp-sdk.git).
I follows the README
first , I download this project: git clone ttps://github.com/proxy-wasm/proxy-wasm-cpp-sdk.git & cd proxy-wasm-cpp-sdk
secondly, docker build -t wasmsdk:v2 -f Dockerfile-sdk .
then, the following picture shows what confused me.

I guess it was emsdk in container, when emcc doing something, errors occurred, maybe libstdc++.so.6 and glibc version is lower ? How can i fix this problem , please help me ~

[zclyne]

I ran into the same error. Wonder this issue is ignored for over half a year..

[PoisWu]

I ran into the same error, too.
I tried to solve the problem by upgrading the version of OS, protobuf3 and emsdk toolchain, I ran into another problems, they are:

• the module isn't compatible to the latest protobuf3 library since some header files are missing. For example, the google/protobuf/generated_message_table_driven.h is missing in the newest version of protobuf3, v24.3
• I followed the version indicate in sdk_container.sh, protobuf3 v. 3.9.1. and emsdk v3.1.7, I can build the docker image successfully but em++ can't compile http_wasm_example.cc. It throw the following error message

PS. The OS I tried is ubuntu:jammy under arm architecture.

[martijneken]

Hi folks, I don't have a direct answer, but in case it helps I'm working on an emsdk update in #157, bumping emsdk from v3.1.7 to v3.1.44. I ran into a different Bazel+Cmake error in that process (now resolved in emsdk), so you might try whether version bump changes anything for you. AFAIK the patch is ready from the ProxyWasmCppSdk point of view -- I'm still looking at Envoy issues.

[krinkinmu]

@martijneken I think this should have been addressed by #172 and is similar to two other issues that were closed.

The PR directly addresses the issue with fail to build the container and removing prebuilt protobuf libraries from the repo and building them from the source should address the issue #155 (comment).

If you want I can test specifically on arm as well to confirm that it does work on both intel and arm platforms.