-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Plugin v0.2.7 and Traefik v2.7+ panic due to reflect.Set #41
Comments
I need to reproduce this on my own, but it looks like an error on Yaegi's side. |
@Michaelhobo, I am sorry, but I cannot reproduce your issue. Can you provide a reproducible use case, using the docker-compose.yaml example file provided in the repository, for example ? |
Here is the docker-compose.yml file I used version: '3.9'
services:
traefik:
image: traefik:v2.7
command:
- --api.insecure=true
- --providers.docker
- --providers.file.filename=/rules-htransformation.yaml
- --log.level=DEBUG
- --experimental.plugins.htransformation.moduleName=github.com/tomMoulard/htransformation
- --experimental.plugins.htransformation.version=v0.2.7
ports:
- 9000:80
- 9001:8080
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ./rules-htransformation.yaml:/rules-htransformation.yaml
- .:/plugins-local/src/github.com/tomMoulard/htransformation/
tty: true
whoami:
image: traefik/whoami # https://github.com/traefik/whoami
command: -name whoami
labels:
traefik.http.routers.whoami.rule: Host(`whoami.localhost`)
traefik.http.routers.whoami.middlewares: htransformation@file Here's the log from running |
Also to clarify, we haven't done the Traefik v3 migration yet, so what I mean by "v2.7+" is really "v2.7 <= x < v3.0". I ran this again with traefik:v3.0, and it does not have that error. |
It seems to be fixed in v2.9 by updating yaegi to include fixes (like this one: traefik/yaegi#1447), so you might want to use traefik v2.9+. |
I'm getting the following error when running htransformation plugin with Traefik v2.7+:
This looks pretty similar to the error in #39
The text was updated successfully, but these errors were encountered: