Community container Latest/Beta tag

[docjyJ]

Is your feature request related to a problem? Please describe.

The AIO containers have a Latest and Beta tag, for the community containers it would be good to have a Latest and Beta tag too, to have a way to test the functionality.

Describe the solution you'd like

Add beta tag to community containers

Describe alternatives you've considered

Idk

Additional context

No

[szaimen]

Hi, interesting idea! However something comparable is already possible and rather the way I would suggest:
if you want the community to test something for you, you can simply adjust the image_tag in the json, e.g. by increasing it one version and it will be tested first by people running the beta channel and afterwards it will be pushed to stable.
I hope this helps?

[docjyJ]

It looks easy to implement.
If you think it's a good idea, I can try to make a PR.

[Zoey2936]

but what if the beta version would require diffrent mounts/env/ports etc. this would mean that either beta would break or latest

[docjyJ]

but what if the beta version would require diffrent mounts/env/ports etc.

It is more complicated, for this specific case we can keep the same method.

PR -> Beta -> Release

Probably a change of port, environment, or volume involves user intervention for migration.
So, no perfect solution...

[szaimen]

but what if the beta version would require diffrent mounts/env/ports etc. this would mean that either beta would break or latest

Yes, true, this is the main reason why it was implemented like how it is currently...

[docjyJ]

Yes, I think the majority of updates do not contain breaking changes.

If the addition of a beta tag is simple, it is an addition that improves the stability of the community container.