You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2021. It is now read-only.
Currently, we write images of the format stackable/zookeeper:3.5.8, but (according to the logs) the agent only actually tries to resolve the package name zookeeper:3.5.8 against all repositories.
The text was updated successfully, but these errors were encountered:
The image field contains an OCI reference. An OCI reference consists of a registry, a repository, and a tag. For instance, the OCI reference "stackable.tech/stackable/zookeeper:3.5.8" consists of the registry "stackable.tech", the repository "stackable/zookeeper", and the tag "3.5.8". The Stackable Agent ignores the registry and considers only the repository and the tag.
In your example "stackable/zookeeper:3.5.8", the registry "stackable" is discarded. The rest of the image path is taken into account.
The question is what a registry is in our scope. If it is a Stackable repository and the Stackable Agent would look up the package only in the specified repository then it would not be possible to create repositories dynamically.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, we write images of the format
stackable/zookeeper:3.5.8
, but (according to the logs) the agent only actually tries to resolve the package namezookeeper:3.5.8
against all repositories.The text was updated successfully, but these errors were encountered: