Releases vs Tags in avalon-docker

[joncameron]

Description

The avalon-docker repository's main branch has a latest release of 7.7.0, but always pulls the latest avalon by default. The current compose file will pull Avalon 8.0. There are tags for each release, but the mismatch is confusing for some users of the docker-based install.

• Should there be a release in addition to the tag for the avalon-docker version corresponding to an Avalon release?
• Is there a better way to do this, or should we remove the releases and only use tags with a rolling main branch?

Done Looks Like

• [ ]

[elynema]

Currently, the avalon-docker 7.7 repo will pull whatever the latest 7.x version is. Docker-compose file should specify the docker tag for the avalon full version + tag avalon-docker when do a release. Then main would be updated to the latest avalon-docker tag.

We have some older versions of avalon-docker that tag less specific versions of avalon. Probably fine to leave those be at this point.

If anyone has an issue, can specify the full version for avalon in the docker-compose file. Could be a problem for someone who is updating versions of 7.x and not moving to the latest version of avalon 7.8.

[elynema]

@cjcolvar fill in Done Looks Like