Sorry Roland we have no plans to provide this.

Here are some of the reasons:

1. We don't know what to include. Some companies will insist in the smallest possible container i.e. just HVR. Others will want to include a repository database. But even if it is just HVR, what database client software should we include? Some run their repository on SQL Server, some on PostgreSQL, some on Oracle, etc.

2. Some components we'd want to include (e.g. some database drivers) require a click through from the user of the software (assuming one agrees to terms and conditions). We cannot do this on behalf of an unknown user.

3. It is not uncommon for organizations to have their preferred minimal configuration (based on a preferred distribution). If we'd deliver something that deviates from it then it is not usable.

4. Some customers use target agents. But many customers also use the hub to write directly to the target. Similar to the considerations for the repository database: what drivers do we include? Snowflake? Databricks? BigQuery? Teradata? Oracle? Etc.

5. Companies tend to want to run different versions of the HVR software, and different versions of integrated components. Very quickly we end up with an unmanageable set of permutations, or we end up with an unusable image.

That said through the community I'd be happy to share a Dockerfile you can use to build your own hub.

Hope this makes sense.
Mark.