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
Currently, the image name of a container on Scarf must match the name on the outgoing registry.
Ie, if user-x publishes a user-x/foo container, and they have the user-x.com pointed to Scarf, the Scarf-based identifier can only be user-x.com/user-x/foo. Ideally, they should be able to configure something like user-x.com/foo as their container identifier through Scarf.
The text was updated successfully, but these errors were encountered:
Currently, the image name of a container on Scarf must match the name on the outgoing registry.
Ie, if
user-x
publishes auser-x/foo
container, and they have theuser-x.com
pointed to Scarf, the Scarf-based identifier can only beuser-x.com/user-x/foo
. Ideally, they should be able to configure something likeuser-x.com/foo
as their container identifier through Scarf.The text was updated successfully, but these errors were encountered: