You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that in the container, uname -a returns different results depending on whether the docker image was built with the CoLiMa agent or the Docker Desktop agent, but both fail the same way anyway
We do have an issue in fp-bindgen for Wasmer 3 support, but it's not exactly trivial and it needs someone to put in the effort: fiberplane/fp-bindgen#185
Wasmer in fiberplane-provider-runtime might need to be bumped to 3
Environment information
The issue was found by @actualwitch while trying to setup a "quickstart" docker image on MacOS for FPD.
Note that the issue seems to be the same as wasmerio/wasmer#3461 which got solved and merged in tree for versions
>= 3.2.0
wasmerio/wasmer@580baebI couldn't find any "release 2" branch in a very quick look, so there might
What happened?
uname -a
returns different results depending on whether the docker image was built with the CoLiMa agent or the Docker Desktop agent, but both fail the same way anywayExpected result
It should start without crashing
The text was updated successfully, but these errors were encountered: