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
Because of the changes in Portainer 2.27, I had to migrate my v2 Templates to v3 by adding the ID parameter to make them work again.
It seems that the former "registry" Tag is not honored anymore and I also had to update all the "image" tags within the JSON to also contain the Registry Server. That is something I was able to change too, so no issue.
But we also have the "network" tag in our Templates to deploy them for certain networks. But this one is not working either anymore, so whenever a User deploys a new application based on a template, he has to select the correct network on his own.
Is there a plan to bring the "network" tag back to v3 templates?
The text was updated successfully, but these errors were encountered:
Because of the changes in Portainer 2.27, I had to migrate my v2 Templates to v3 by adding the ID parameter to make them work again.
It seems that the former "registry" Tag is not honored anymore and I also had to update all the "image" tags within the JSON to also contain the Registry Server. That is something I was able to change too, so no issue.
But we also have the "network" tag in our Templates to deploy them for certain networks. But this one is not working either anymore, so whenever a User deploys a new application based on a template, he has to select the correct network on his own.
Is there a plan to bring the "network" tag back to v3 templates?
The text was updated successfully, but these errors were encountered: