使用go1.24+sdk编译wasm文件，docker运行报错【 Failed to load Wasm module due to a missing import: wasi_snapshot_preview1.sched_yield】

[loli0123456789]

大佬好 @erasernoob ，

解决了go1.24+（不使用tinygo）编译wasm文件报错的问题，
现在是通过docker本地调试wasm文件报错，在docker compose up命令执行后
镜像为【higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/gateway:v2.0.7】的容器启动失败，
还得麻烦大佬再给看下。

基础环境

相关操作参考文档链接：https://higress.cn/docs/latest/user/wasm-go/?spm=36971b57.66c7e6fb.0.0.75f66177l0ly2a
本地机器操作系统：Windows 11，go版本：1.24.5
执行编译命令：
$env:GOOS = "wasip1"
$env:GOARCH = "wasm"
go build -buildmode=c-shared -o main.wasm ./

报错如下：

[2025-07-23 07:36:24.853][1][info][main] [external/envoy/source/server/server.cc:840] runtime: {}
[2025-07-23 07:36:24.854][1][info][admin] [external/envoy/source/server/admin/admin.cc:66] admin address: 0.0.0.0:9901
[2025-07-23 07:36:24.854][1][info][config] [external/envoy/source/server/configuration_impl.cc:144] loading tracing configuration
[2025-07-23 07:36:24.854][1][info][config] [external/envoy/source/server/configuration_impl.cc:103] loading 0 static secret(s)
[2025-07-23 07:36:24.854][1][info][config] [external/envoy/source/server/configuration_impl.cc:109] loading 1 cluster(s)
[2025-07-23 07:36:24.858][1][info][config] [external/envoy/source/server/configuration_impl.cc:113] loading 1 listener(s)
[2025-07-23 07:36:24.862][1][info][router] [external/envoy/source/common/router/config_impl.cc:725] route stats is , name is
[2025-07-23 07:36:25.325][1][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:122] Base Wasm created 1 now active
[2025-07-23 07:36:25.940][1][error][wasm] [external/envoy/source/extensions/common/wasm/wasm_vm.cc:41] Failed to load Wasm module due to a missing import: wasi_snapshot_preview1.sched_yield
[2025-07-23 07:36:25.940][1][error][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:151] Wasm VM failed Failed to initialize Wasm code
[2025-07-23 07:36:25.940][1][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:191] ~Wasm 0 remaining active
[2025-07-23 07:36:25.941][1][critical][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:547] Plugin configured to fail closed failed to load
[2025-07-23 07:36:25.948][1][critical][main] [external/envoy/source/server/server.cc:134] error initializing config ' /etc/envoy/envoy.yaml': Unable to create Wasm HTTP filter wasmdemo
[2025-07-23 07:36:25.949][1][info][main] [external/envoy/source/server/server.cc:992] exiting
Unable to create Wasm HTTP filter wasmdemo

[CH3CHO]

用2.1.5的gateway镜像试试呢

…

---- 回复的原邮件 ---- | 发件人 | ***@***.***> | | 发送日期 | 2025年07月23日 17:11 | | 收件人 | ***@***.***> | | 抄送人 | Subscribed ***@***.***> | | 主题 | [higress-group/higress-group.github.io] 使用go1.24+sdk编译wasm文件，docker运行报错【 Failed to load Wasm module due to a missing import: wasi_snapshot_preview1.sched_yield】 (Issue #448) | loli0123456789 created an issue (higress-group/higress-group.github.io#448) 大佬好 @erasernoob ， 解决了go1.24+（不使用tinygo）编译wasm文件报错的问题， 现在是通过docker本地调试wasm文件报错，在docker compose up命令执行后 镜像为【higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/gateway:v2.0.7】的容器启动失败， 还得麻烦大佬再给看下。 基础环境 相关操作参考文档链接：https://higress.cn/docs/latest/user/wasm-go/?spm=36971b57.66c7e6fb.0.0.75f66177l0ly2a 本地机器操作系统：Windows 11，go版本：1.24.5 执行编译命令： $env:GOOS = "wasip1" $env:GOARCH = "wasm" go build -buildmode=c-shared -o main.wasm ./ 报错如下： [2025-07-23 07:36:24.853][1][info][main] [external/envoy/source/server/server.cc:840] runtime: {} [2025-07-23 07:36:24.854][1][info][admin] [external/envoy/source/server/admin/admin.cc:66] admin address: 0.0.0.0:9901 [2025-07-23 07:36:24.854][1][info][config] [external/envoy/source/server/configuration_impl.cc:144] loading tracing configuration [2025-07-23 07:36:24.854][1][info][config] [external/envoy/source/server/configuration_impl.cc:103] loading 0 static secret(s) [2025-07-23 07:36:24.854][1][info][config] [external/envoy/source/server/configuration_impl.cc:109] loading 1 cluster(s) [2025-07-23 07:36:24.858][1][info][config] [external/envoy/source/server/configuration_impl.cc:113] loading 1 listener(s) [2025-07-23 07:36:24.862][1][info][router] [external/envoy/source/common/router/config_impl.cc:725] route stats is , name is [2025-07-23 07:36:25.325][1][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:122] Base Wasm created 1 now active [2025-07-23 07:36:25.940][1][error][wasm] [external/envoy/source/extensions/common/wasm/wasm_vm.cc:41] Failed to load Wasm module due to a missing import: wasi_snapshot_preview1.sched_yield [2025-07-23 07:36:25.940][1][error][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:151] Wasm VM failed Failed to initialize Wasm code [2025-07-23 07:36:25.940][1][debug][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:191] ~Wasm 0 remaining active [2025-07-23 07:36:25.941][1][critical][wasm] [external/envoy/source/extensions/common/wasm/wasm.cc:547] Plugin configured to fail closed failed to load [2025-07-23 07:36:25.948][1][critical][main] [external/envoy/source/server/server.cc:134] error initializing config ' /etc/envoy/envoy.yaml': Unable to create Wasm HTTP filter wasmdemo [2025-07-23 07:36:25.949][1][info][main] [external/envoy/source/server/server.cc:992] exiting Unable to create Wasm HTTP filter wasmdemo — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[loli0123456789]

可以了！大赞！！
那文档里，这块也可以改下了

用2.1.5的gateway镜像试试呢
…

[erasernoob]

感谢帮忙指出错误~

[Sun-Kas]

你好，我也遇到了相同的问题，更改版本后成功运行，但是在测试时遇到

C:\Users\13445>curl http://127.0.0.1:10000/get
Not Found

并没有返回网关处理后的请求头的内容（注：curl http://127.0.0.1:12345/get是正常的）；
请问一下这个怎么解决

[erasernoob]

你好，我也遇到了相同的问题，更改版本后成功运行，但是在测试时遇到

C:\Users\13445>curl http://127.0.0.1:10000/get Not Found

并没有返回网关处理后的请求头的内容（注：curl http://127.0.0.1:12345/get是正常的）； 请问一下这个怎么解决

可以贴一下 docker compose logs envoy 网关层的详细日志

[loli0123456789]

两位好，刚试了下，我的是可以的。
我们试着确认几点内容：

1、确认wasm所在容器是否部署成功

1）访问：http://localhost:9901/ 是否可以正常访问，这个是gateway管理页面，说明gateway本身没啥问题
注：我下面的compose文件增加了9901端口映射
访问：http://localhost:10000/ 是否可以正常访问，这个应该已经转发httpbin页面了

2、检查docker-compose文件

version: '3.7'
services:
envoy:
image: higress-registry.cn-hangzhou.cr.aliyuncs.com/higress/gateway:v2.1.5
entrypoint: /usr/local/bin/envoy
# 注意这里对wasm开启了debug级别日志，正式部署时则默认info级别
command: -c /etc/envoy/envoy.yaml --component-log-level wasm:debug
depends_on:
- httpbin
networks:
- wasmtest
ports:
- "10000:10000"
- "9901:9901"
volumes:
- ./envoy.yaml:/etc/envoy/envoy.yaml
- ./main.wasm:/etc/envoy/main.wasm

httpbin:
image: kennethreitz/httpbin:latest
networks:
- wasmtest
ports:
- "12345:80"

networks:
wasmtest: {}

3、检查envoy.yaml文件

admin:
address:
socket_address:
protocol: TCP
address: 0.0.0.0
port_value: 9901
static_resources:
listeners:

• name: listener_0
  address:
  socket_address:
  protocol: TCP
  address: 0.0.0.0
  port_value: 10000
  filter_chains:
  • filters:
    • name: envoy.filters.network.http_connection_manager
      typed_config:
      "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
      scheme_header_transformation:
      scheme_to_overwrite: https
      stat_prefix: ingress_http
      route_config:
      name: local_route
      virtual_hosts:
      - name: local_service
      domains: ["*"]
      routes:
      - match:
      prefix: "/"
      route:
      cluster: httpbin
      http_filters:
      • name: wasmdemo
        typed_config:
        "@type": type.googleapis.com/udpa.type.v1.TypedStruct
        type_url: type.googleapis.com/envoy.extensions.filters.http.wasm.v3.Wasm
        value:
        config:
        name: wasmdemo
        vm_config:
        runtime: envoy.wasm.runtime.v8
        code:
        local:
        filename: /etc/envoy/main.wasm
        configuration:
        "@type": "type.googleapis.com/google.protobuf.StringValue"
        value: |
        {
        "mockEnable": false
        }
      • name: envoy.filters.http.router
        typed_config:
        "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router
        clusters:
• name: httpbin
  connect_timeout: 30s
  type: LOGICAL_DNS

  Comment out the following line to test on v6 networks

  dns_lookup_family: V4_ONLY
  lb_policy: ROUND_ROBIN
  load_assignment:
  cluster_name: httpbin
  endpoints:
  • lb_endpoints:
    • endpoint:
      address:
      socket_address:
      address: httpbin
      port_value: 80