How do I start a single container with traefik?

[luigir-it]

Hi. I'm using this plugin with traefik.

Let's say I have 10 containers, each one configured with traefik using the file provider
Those containers are "independent" from each other, and I'd like to start only the one I'm accessing to.

Right now, I have a plugin section with the names of all the containers (comma separated list). This way, when I access a container (e.g. 3), all 10 are started.

http:
  middlewares:

    sablier-dynamic:
      plugin:
        sablier:
          names: 0,1,2,3,4,5,6,7,8,9
          sablierUrl: http://sablier-traefik:10000
          sessionDuration: 1m
          dynamic:
            displayName: Application
            refreshFrequency: 2s
            showDetails: "true"
            theme: ghost

Does that mean that I have to replicate the plugin section 10 times, and have only a container name per section?

[acouvreur]

Hi @luigir-it

Exactly, one plugin configuration per application set.

So if you only have one application every time, you will have 10 plugin entries.

You will be able to customized every entry, such as the theme, display name, loading strategy and session duration!

Does that make sense ? It seems like you've already figured out though 😁

[luigir-it]

Hi and thanks for answering.

Does that make sense ?

It does if you favor customization over simplicity.

My use case is very simple. I have many containers and not much RAM. I don't need the containers to be up all the time.

I would much prefer to have a single plugin middleware being shared across all the containers.

I don't know if the plugin has the knowledge of which container the traffic will be forwarded to. Probably not, but it knows its ip for sure. If sablier and the aforementioned container share the same network, then this would completely eliminate the need to specify names or group, and the configuration will be much cleaner and easy to manage.

[luigir-it]

I don't speak English natively so tell me if something is not clear

[acouvreur]

Probably not, but it knows its ip for sure.

It does not, when containers are shutdown to zero, we cannot infer the actual underlying container from the packet itself.

We can infer it from traefik by matching the router to the matched container, but then again we have to do API calls to the reverse proxy...

This would be a very costly integration between Sablier and Traefik for the docker provider specifically.