pitrho/rancher-gen

File generator that renders templates using Rancher API.

rancher-gen's Issues

Can you provide an executable?

Hi,

nice project. Thank you very much.

Is there a chance, that you could provide an executable file without the need of python installed on the system. For example through PyInstaller?

The background of my question is, that often inside docker containers there is no python installed.
An executable would eleminate the need of installing python inside the container.

Kind Regards

allow to trigger initial generation immediately

First of all, let me say thanks for this great project, I'm trying to build an auto-configuring Traefik setup with it.

Suppose there are already some containers running and my container with rancher-gen is not the first to start. However, rancher-gen is supposed to generate the configuration file for my reverse proxy in order to route traffic to containers based on the host names of the requests.

It looks like rancher-gen currently does not trigger immediately when it is invoked, but only when Rancher reports some changes. So I would now have to wait for some change in Rancher before any configuration gets generated, which is not really acceptable. I think I need some capability to trigger an initial generation run.

What do you think?

How to build this project？

Hi，i don't know how to build this project.Because i will modify some code in my company env.

reported data only includes changed containers

This is somewhat related to #1 .

Let's say I have a lot of containers for which I need to generate configuration files. It looks like rancher-gen only has knowledge of those containers which actually did change, not all containers in the system. So my template which looks something like

{% for container in containers %}
  id {{container['id']}}, name {{container['name']}}, state {{container['state']}}
{% endfor %}

only contains one line for the container which actually changed, instead of all containers (which is what I would have expected). That also means that whenever a container changes, the (single) config file is overridden, and any information about previous containers is lost.

Is this how rancher-gen is supposed to work, or am I missing something?

Get containers by label or env vars?

With docker-gen it's possible to get containers by env var. Is it possible with rancher-gen too?
Not limited to a project / stack service?
Just all containers in a rancher environment by label or env var.