-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K3s uses incorrect wasm shims names #9650
Comments
Interesting I didn't hit this initially because I was writing out the runtime information on the nodes manually. |
##Environment Details Infrastructure
Node(s) CPU architecture, OS, and version: Linux 5.14.21-150500.53-default x86_64 GNU/Linux Cluster Configuration:
Config.yaml:
Reproduction
Results: Existing release results - all binaries installed before installing k3s $ ls /usr/local/bin/
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/config.toml
After latest COMMIT_ID install $ ls /usr/local/bin/
$ sudo cat /var/lib/rancher/k3s/agent/etc/containerd/config.toml
$ kgp
$ export PUBLIC_IP=$(kubectl get ingress wasm-ingress -o jsonpath='{.status.loadBalancer.ingress[0].ip}') $ curl -v http://$PUBLIC_IP/slight/hello
$ curl -v http://$PUBLIC_IP/spin/go-hello
$ curl -v http://$PUBLIC_IP/spin/hello
|
from @flavio in #9519
K3s should use correct binary names and the associated RuntimeType. There was quite a mixup between v1 and v2 shims.
The text was updated successfully, but these errors were encountered: