crc: [BUG] my-connect-cluster-connect-source:1.2.0 builder image 404

I was able to start up a kafka cluster using the AMQ Streams operator in the new openshift 4 crc on my mac laptop. However, when I run oc start-build my-connect-cluster-connect --from-dir=/Users/dpeterso/debezium, I get the following error: The ImageStreamTag “my-connect-cluster-connect-source:1.2.0” is invalid: from: Error resolving ImageStreamTag my-connect-cluster-connect-source:1.2.0 in namespace es-rhug-demo: unable to find latest tagged image. I also attached an image showing a 404 error when drilling down to where the image reference is in the openshift 4 console of my project. Operators are new to me, is this a bug or am I just missing a step where I somehow have control over getting that image onto my machine?

General information

  • OS: macOS
  • Hypervisor: hyperkit
  • Did you run crc setup before starting it (Yes/No)? Yes

CRC version

version: 1.0.0-beta.3-4.1.11+e97bf65

CRC status

CRC VM:          Running
OpenShift:       Running (v4.x)
Disk Usage:      12.82GB of 32.2GB (Inside the CRC VM)
Cache Usage:     10.48GB
Cache Directory: /Users/dpeterso/.crc/cache

CRC config

- bundle                             : /Users/dpeterso/.crc/crc_hyperkit_4.1.11.crcbundle
- cpus                               : 4
- memory                             : 8192
- nameserver                         : 
- pull-secret-file                   : 
- vm-driver                          : hyperkit
- warn-check-bundle-cached           : true

Host Operating System

ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G95

Steps to reproduce

  1. Installed AMQ Streams operator
  2. Started Kafka cluster
  3. Followed instructions here: https://debezium.io/documentation/reference/0.9/operations/amq-streams.html
  4. After downloading plugin, I ran the command in the instructions from step 3 above: oc start-build my-connect-cluster-connect --from-dir=/Users/dpeterso/debezium

Expected

The command would run successfully

Actual

The ImageStreamTag “my-connect-cluster-connect-source:1.2.0” is invalid: from: Error resolving ImageStreamTag my-connect-cluster-connect-source:1.2.0 in namespace es-rhug-demo: unable to find latest tagged image

Logs

INFO Checking if oc binary is cached              
DEBU oc binary already cached                     
INFO Checking if HyperKit is installed            
DEBU Checking if hyperkit is installed            
INFO Checking if crc-driver-hyperkit is installed 
DEBU Checking if crc-driver-hyperkit is installed 
DEBU crc-driver-hyperkit is already installed in /Users/dpeterso/.crc/bin/crc-driver-hyperkit 
INFO Checking file permissions for /etc/resolver/testing 
INFO Checking file permissions for /etc/hosts     
INFO Checking if CRC bundle is cached in '$HOME/.crc' 
Checking file: /Users/dpeterso/.crc/machines/crc/.crc-exist
Found binary path at /Users/dpeterso/.crc/bin/crc-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address 127.0.0.1:59316
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(crc) Calling .GetBundleName
(crc) Calling .DriverName
(crc) Calling .GetState
(crc) DBG | exe=/Users/dpeterso/.crc/bin/crc-driver-hyperkit uid=0
(crc) DBG | hyperkit pid from json: 1572
Making call to close driver server
(crc) Calling .Close
Successfully made call to close driver server
Making call to close connection to plugin binary
CodeReady Containers instance is running

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 17 (7 by maintainers)

Most upvoted comments

I was able to get builds working by following Fernando’s advice above:

$ oc create secret generic mysecret
--from-file .dockerconfigjson=${XDG_RUNTIME_DIR}/containers/auth.json
--type=kubernetes.io/dockerconfigjson

This links the secret to the builder service account, that runs S2I builds.

$ oc secrets link builder mysecret

auth.json is just my pull secret text file downloaded and renamed