Configurable Container Registry & Artifact Repositories

[hennlo]

Affected Areas

DB, UI

Feature Description

Add the possibility to change the default container registry where docker images are pulled from if a docker deployment of stores is desired.

Currently this always defaults to: https://registry-1.docker.io/v2.

Use Case(s)

Currently any pull of container images defaults to: https://registry-1.docker.io/v2.

However if Polypheny runs behind a company proxy or within a hardened environment without direct internet access, container images cannot be pulled on the fly. This results in a timeout.

However many companies use artifact repositories with virtual mirrors that act as artifact proxies to obtain the data from the internet cache it internally and configure hardened systems to pull artifacts like container images directly from this local repository.

Possible Solutions

Add a configuration parameter that allows the specification of 1..n additional artifact repositories that result in usable instances that can be configured or added to docker environments as additional parameters.

That way each container instance can have its configuration from where it wants to pull images. Because some remote docker engines might even have direct access to the internet

By default there only exists one artifact repository default=https://registry-1.docker.io/v2 But you could add more named repositories and even have another configuration parameter that specifies the default_repository that is automatically selected if configured via UI or if its omitted when creating a new docker engine connection.

Possible Alternatives

A workaround would be also to not pull the image each time but check locally first if the image is already cached on the engine.