Skip to content

I'm failing to install a Codefresh Runner #864

Closed

Description

@gilchaouat

Running: codefresh runner init --token 66bda17e83c9d96415e86d2d.0f07c7843555031dfe69604c32ae2e0c

Getting:
Previous installation state:
✘ run cluster acceptance tests
◼ generate new agent name
◼ create new agent
◼ install new agent
◼ generate new runtime name
◼ create new runtime
◼ update runtime environment images with docker-registry url
◼ update runtime environment with env vars and resources
◼ set new runtime as default
◼ add cluster integration
◼ install runtime
◼ install app-proxy
◼ update runtime environment app proxy ip
◼ update agent with new runtime
◼ attach runtime to agent
◼ install cluster monitoring
◼ generate helm value files
◼ create test pipeline
◼ execute test pipeline
? Detected previous incomplete installation, do you want to resume this installation? No
This installer will guide you through the Codefresh Runner installation process
? Name of Kubernetes context to use minikube
? Kubernetes namespace to install into (will be created if it does not exist) codefresh
? Set this as the default runtime environment for your Codefresh account? No
? Run demo pipeline after install? Yes

Installation options summary:
1. Kubernetes Context: minikube
2. Kubernetes Namespace: codefresh
3. Set this as default account runtime-environment: false
4. Execute demo pipeline after install: true
5. HTTP proxy: none
6. HTTPS proxy: none
7. No proxy: none

Updated context: cf-runner
Switched to context: cf-runner
A Codefresh context named 'cf-runner' was added to your "cfconfig" file.
executing step: run cluster acceptance tests
venona component upgrade is required, downloading.
downloading [████████████████████████████████████████] 100% | 26098486/26098486
Error: Failed to run cluster acceptance tests: failed to download venona, aborting.

Activity

  1. nodoyuna commented on Nov 2, 2024

    @nodoyuna

    HI @gilchaouat, Could you resolve the issue? I’m at the same point and don’t know how to proceed, plus Codefresh support isn’t responding.

  2. mgoodfellow commented on Dec 9, 2024

    @mgoodfellow

    I've just been fighting with this too - seems that the cli approach is deprecated: https://codefresh.io/docs/docs/installation/runner/install-codefresh-runner/

    Instead you use the helm chart to install: https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime#chart-configuration

    kubectl get pods -n codefresh
    NAME                                             READY   STATUS    RESTARTS   AGE
    cf-runtime-lv-monitor-6798d                      1/1     Running   0          9m44s
    cf-runtime-lv-monitor-f5k89                      1/1     Running   0          9m44s
    cf-runtime-lv-monitor-nlddq                      1/1     Running   0          9m44s
    cf-runtime-runner-8467b97cc9-b6w2d               1/1     Running   0          9m44s
    cf-runtime-volume-provisioner-777d98987d-fjswv   1/1     Running   0          9m44s
    

    Hope this is of some use - the runner seems to have automatically registered itself in my account:

    image

  3. masontikhonov commented on Nov 18, 2026

    @masontikhonov
    Contributor

    CLI-based installation is deprecated, please use Helm chart: https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions