Skip to content
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

Custom templates: "No templates available." #922

Closed
jangrewe opened this issue Jun 11, 2017 · 6 comments
Closed

Custom templates: "No templates available." #922

jangrewe opened this issue Jun 11, 2017 · 6 comments
Labels
Milestone

Comments

@jangrewe
Copy link

jangrewe commented Jun 11, 2017

Description

I'm using custom templates, and i can see that the request to /api/templates?key=containers returns my JSON, but the App Templates page just says "No templates available."

  1. Set custom templates URL in settings
  2. Go to App Templates page

Technical details:

  • Portainer version: 1.13.2
  • Target Docker version (the host/cluster you manage): 17.05.0-ce
  • Platform (windows/linux): linux
  • Command used to start Portainer: /usr/bin/docker run --name portainer -v "/var/run/docker.sock:/var/run/docker.sock" -v "/srv/portainer:/data" -p 6000:9000 portainer/portainer
  • Target Swarm version (if applicable): -
  • Browser: Firefox 53.0.3 64bit

It doesn't work with 1.13.1 and 1.13.0 either (when using --templates), but works fine with 1.12.4

@deviantony
Copy link
Member

@jangrewe could you share your JSON definitions?

@jangrewe
Copy link
Author

Here's an abbreviated version which doesn't work:

[
  {
    "title": "Registry",
    "description": "Docker image registry",
    "logo": "https://faked.org/portainer/logos/registry.png",
    "image": "registry:latest",
    "ports": [
      "5000/tcp"
    ],
    "volumes": ["/var/lib/registry"]
  }
]

@BrookofClay
Copy link

I had a similar issue when setting up custom templates.

For me adding the platform of the template to the JSON def seemed to fix this and my templates appeared without issue.

@deviantony
Copy link
Member

I've been able to reproduce this, indeed it seems that adding the platform field solves the problem. Will fix as this field should be optional.

@deviantony deviantony added this to the 1.13.x milestone Jun 12, 2017
@jangrewe
Copy link
Author

Thanks, adding this field fixes it!

@deviantony
Copy link
Member

I'll keep this issue open as the platform field is documented as optional. Will be fixed in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants