Add docker labels

[fvalle1]

Is your feature request related to a problem? Please describe. I'm always frustrated when I cannot add labels to my containers

Describe the solution you'd like Add a label parameter as environment and ports

Describe alternatives you've considered deploy containers on my own

Additional context

[Plarpoon]

Fully agree, this one is pretty much mandatory, using docker without labels is like having a car without breaks. You can use it and it works but you really don't want to use it.

[locomoco28]

This feature would be really useful for using stuff like Traefik or in my case lucaslorentz/caddy-docker-proxy. I don't wanna expose apps on local ports like 127.0.0.1:3001, :3002, :3003 etc. and have to proxy requests to each port in an extra config file or web interface. I just want to modify the apps in Casa to have the caddy: my-app.domain.com caddy.reverse_proxy: "{{ upstreams 80}}" It just makes everything so much easier to set up

[EthraZa]

Any news about that?

[coraunderhill]

For anyone else hoping for a response on this, using Portainer is a means to an end until this becomes a feature.

[frostbytedata]

The issue with using Portainer in conjunction with CasaOS to manage the labels, is it seems that anytime I restart an app from the Casa Dashboard, it wipes my custom Labels that I assigned to the container in Docker. Anyone know a better way to configure them so they stick even when the container is restarted or recreated by Casa?

[rahjr42]

+1 to this so I can use TSDproxy - https://almeidapaulopt.github.io/tsdproxy/docs/ It requires labels to trigger it to add the container to the tailnet.

[mrpunkin]

I'd also like to request this.

[david-w-t]

This is a highly needed feature.

[skorpeyon]

I'd also like to request this. Just installed Flame Dashboard and am unable to use Docker integration without using Portainer to add labels, and then have to remember to never restart a container directly through CasaOS. Seems like a much-needed feature.