Lissy93
Unable to Install Template or Edit Configuration - Portainer Community Edition 2.27.0 LTS
Hello everyone! Installed and enjoyed this great file last week. I then upgraded to CE 2.27.0 LTS. Now, when I view the template list and click on a template, the configuration area at the top of the page displays briefly, then goes away and shows the list again. Any ideas? I tried re-pulling the containers, rebooting and clearing the broswer cache. I then reset the default portainer list, which seems to work fine. Must be something with the Lissy93 list?
Seems to be related to this issue: https://github.com/portainer/portainer/issues/12337 Reverting to portainer-ce:2.21.3 is the quickest solution.
Reverting to portainer-ce:2.21.3 is the quickest solution.
What is the most effective method to do this?
This template list works for me: https://raw.githubusercontent.com/TomChantler/portainer-templates/refs/heads/v3/templates_v3.json
I looked at this too. It hasn't been generated since Nov 2024 whereas the lissy one is as of March 2025.
Same issue here. Fresh install, same behaviour. 2.27.2 LTS, however, if I use this URL https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/template/portainer-v3-amd64.json, then this is not an issue. It would seem the āportainer-templates/templates.jsonā JSON version might need an upgrade to Version 3. As the other URL works fine.
This template list works for me: https://raw.githubusercontent.com/TomChantler/portainer-templates/refs/heads/v3/templates_v3.json
yep this seems to be because of the template chamge from v2 to v3 which this is v3 templatethanks for sharing it works for me too =)
Reiterating that the repo above hasn't been generated since Nov 2024 whereas the Lissy one is as of March 2025. Ideally the repo maintainer would add an automatic converter for v3 since this content is more recent.
There's a PR waiting for merge that fixes this issue. Until then, either roll back to an earlier portainer release or use a different URL.
It seems Lissy may have abandoned this repo, or just hasn't the time for merging the PR above. It's from November 2024. The only issue I have with using Tom's repo is that it's an old snapshot and doesn't include any of the new auto generated data that Lissy's repo does.
I only recently returned to actively building my Home Lab servers after recent server failures and corruption (including backups). I was planning to use Portainer together with Stack and Container Templates, but apart from Portainer's default templates, I have been unable to get any of the available to work. What I have been able to identify is that at in a some point, Portainer has updated their Template JSON format from Version 2 to Version 3. It is unclear to me in my search of Portainer's documentation what has changed. Every set of Application Templates I found was based on Version 2 and hence exhibits the same issues documented about. I also tried Portainer's Version 2 Templates and they also have the same issues! Ideally it would be great to build a simple script to translate Version 2 Templates into Version 3 Templates. I'm hoping that this helps explain some or all of the issues, but I'm continuing to analyse and resolve this problem.
@ScottJWalter This PR seems to be merged, ~but still the same issue~.
nevermind, just read the PR, it added new file with _v3 suffix and it seems to work. https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates_v3.json
While good that @Lissy93 merged the file into the repo, this is still the same file TomChantler created 5 months ago. If you've been using his file over on his fork, this is the same one. Ideally the file would be auto generating alongside the non v3 one (or, why need the non v3 if future Portainer versions cannot use it).
I took a stab in my fork convert them to be v3 compatible... Kind of worked, but I would guess that there are bugs, just ChatGPT vibe coding bulk of the conversion code when I gave schema for v2 and v3. I will use it for myself, but I will not make PR based on LLM code.
There needs to be two version of Lissy93, one for arm7-8 and x86, the issue is, users have a choice to pick from based on the user architect to work correctly, or the user will have issue with functionality with stand choice. Something too think about.
There needs to be two version of Lissy93, one for arm7-8 and x86, the issue is, users have a choice to pick from based on the user architect to work correctly, or the user will have issue with functionality with stand choice. Something too think about.
I would guess that would fall under another separate issue to support arm.