-
Notifications
You must be signed in to change notification settings - Fork 52
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
Maximum recursion depth exceeded - Traefik #99
Comments
Fixed it commenting the Ran sudo make update
Updating from Git repo...
Already up to date.
Updating variable names
Updating Traefik variables
Update finished
Then checked
|
Thanks for the report! At a quick glance, it looks like I may have messed up the command used to replace hmsdocker_traefik_static_config_location: "{{ traefik_ext_hosts_configs_path | default(hms_docker_apps_path + '/traefik/config/static_confs/') }}" I've pushed a fix for this in another branch (cd947ec) that I hope to merge soon. Just to confirm, this was an existing install and Traefik was completely disabled? |
Yes, that was an existing install from what I'd say was v0.0. And yeah, traefik was completely disabled (I had the container disabled but don't remember if I switched off anything else manually) I can share the config files though. |
Sweet thanks for the info. I think this issue occurred during the variable "compilation" process of Ansible, so even with Traefik fully disabled this would still happen. The fix will be merged in shortly along with some other massive changes. |
OS: Ubuntu 24.04 LTS
Ansible: core 2.17.1
Docker: 27.0.2
Updating from version 0.0 to 1.4, I got an
maximum recursion depth exceeded
exception error in thehmsdocker : Ensure docker-compose.yml file.
task.I pulled the latest changes, migrated vars, updated vars using make update and ran the playbook and this error arised. Seems like there is an issue with something related to traefik. Noticed there was a var change there but I don't even have traefik enabled.
Pasting the full log:
The text was updated successfully, but these errors were encountered: