ockerhub --type docker -in

Example Command OutputPlease enter a name for the service connector [dockerhub]:

Please enter a description for the service connector []:

Please select a service connector type (docker) [docker]:

Only one resource type is available for this connector (docker-registry).

Only one authentication method is available for this connector (password). Would you like to use it? [Y/n]:

Please enter the configuration for the Docker username and password/token authentication method.

[username] Username {string, secret, required}:

[password] Password {string, secret, required}:

[registry] Registry server URL. Omit to use DockerHub. {string, optional}:

Successfully registered service connector `dockerhub` with access to the following resources:

┏━━━━━━━━━━━━━━━━━━━━┯━━━━━━━━━━━━━━━━┓

┃   RESOURCE TYPE    │ RESOURCE NAMES ┃

┠────────────────────┼────────────────┨

┃ 🐳 docker-registry │ docker.io      ┃

┗━━━━━━━━━━━━━━━━━━━━┷━━━━━━━━━━━━━━━━┛

This Service Connector does not support generating short-lived credentials from the username and password or token credentials configured in the Service Connector. In effect, this means that the configured credentials will be distributed directly to clients and used to authenticate directly to the target Docker/OCI registry service.

Auto-configuration

This Service Connector does not support auto-discovery and extraction of authentication credentials from local Docker clients. If this feature is useful to you or your organization, please let us know by messaging us in Slack or creating an issue on GitHub.

Local client provisioning

This Service Connector allows configuring the local Docker client with credentials:

zenml service-connector login dockerhub

Example Command Output

Attempting to configure local client using service connector 'dockerhub'...

WARNING! Your password will be stored unencrypted in /home/stefan/.docker/config.json.

Configure a credential helper to remove this warning. See