Registry login

Node catalog Actions

On this page

Usage and specifics

The Registry credential stores a username and password or token. Check the registry domain and push permissions.

Technical type : ci_docker_login. Runtime : docker.

Credentials and prerequisites

Create and configure the credential : registry

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.

Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

Parameter	Type	Default	Values / limits
`registry`	`string`	`"ghcr.io"`	-; min 1
`credentialId`	`string`	`""`	-; min 1
`executionTarget`	`union`	`{"kind":"host"}`	-
`executionTarget.kind`	`literal`	`"host"`	`host`, `remote_server`, `kube`, `swarm`
`executionTarget.serverId`	`string`	-	-; min 1
`executionTarget.provider`	`enum`	-	`aws`, `gcp`, `scaleway`, `ovh`, `azure`, `digitalocean`, `hetzner`
`executionTarget.clusterId`	`string`	-	-; min 1
`executionTarget.namespace`	`string`	-	-

Configuration help

registry Registry: Docker registry host (e.g. ghcr.io, docker.io).
credentialId Registry credential: Credential with push/pull access to the registry.

Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

json

{
  "registry": "ghcr.io",
  "credentialId": "",
  "executionTarget": {
    "kind": "host"
  }
}

Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.