Switching to non-Quay registry such as Artifactory Docker registry

[jauyzed]

Hello! We are using artifactory as image registry but we do not have access to GUI dashboard yet due to .testing TLD issue. Is there a way to configure crc to connect to artifactory registry as default?

Thanks!

[praveenkumar]

https://docs.openshift.com/container-platform/4.11/openshift_images/image-configuration.html#images-configuration-file_image-configuration have all the details and it is not CRC specific query but openshift one.

[jauyzed]

@praveenkumar How are the credentials/authentication managed for a docker registry like artifactory?

I added the new registry(Artifactory). I do not see the change being reflected in /etc/containers/policy.json

Original image.config.openshift.io/cluster

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: config.openshift.io/v1
kind: Image
metadata:
  annotations:
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
    release.openshift.io/create-only: "true"
  creationTimestamp: "2022-08-24T04:21:53Z"
  generation: 2
  name: cluster
  ownerReferences:
  - apiVersion: config.openshift.io/v1
    kind: ClusterVersion
    name: version
    uid: 8f868148-c3f5-4372-961e-27ea1df4e130
  resourceVersion: "19564"
  uid: c173d90e-d8f5-42cf-bb1a-33efa8738ed4
spec:
  additionalTrustedCA:
    name: registry-certs
status:
  externalRegistryHostnames:
  - default-route-openshift-image-registry.apps-crc.testing
  internalRegistryHostname: image-registry.openshift-image-registry.svc:5000

Modified:

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: config.openshift.io/v1
kind: Image
metadata:
  annotations:
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
    release.openshift.io/create-only: "true"
  creationTimestamp: "2022-08-24T04:21:53Z"
  generation: 2
  name: cluster
  ownerReferences:
  - apiVersion: config.openshift.io/v1
    kind: ClusterVersion
    name: version
    uid: 8f868148-c3f5-4372-961e-27ea1df4e130
  resourceVersion: "19564"
  uid: c173d90e-d8f5-42cf-bb1a-33efa8738ed4
spec:
  allowedRegistriesForImport:
    - domainName: fbbd1.fb
      insecure: false
  additionalTrustedCA:
    name: registry-certs
  registrySources:
    allowedRegistries:
    - fbbd1.fb
status:
  externalRegistryHostnames:
  - default-route-openshift-image-registry.apps-crc.testing
  internalRegistryHostname: image-registry.openshift-image-registry.svc:5000

[praveenkumar]

https://docs.openshift.com/container-platform/4.11/openshift_images/image-streams-manage.html#images-imagestream-import-images-private-registry_image-streams-managing you should add pull secrets for that.