question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Failed to start a workspace on a minikube cluster

See original GitHub issue

Describe the bug

There are several issues, that user might face during starting up a workspace on the minikube cluster. Basically because of pulling Universal developer image which takes around ~15 min.

  1. ImagePullBackOff error ImagePullBackOff

Solution: restart the minikube cluster with the additional flag --kubernetes-version=v1.23.9


  1. 'Starting' for longer than timeout error screenshot-192 168 39 246 nip io-2022 08 19-16_53_19

Solution: Create a WorkspaceOperatorConfig:

apiVersion: controller.devfile.io/v1alpha1
kind: DevWorkspaceOperatorConfig
metadata:
  name: devworkspace-operator-config
  namespace: devworkspace-controller
config:
  workspace:
    progressTimeout: 30m

  1. The workspace status remains "Starting" in the last 300 seconds error screenshot-192 168 39 246 nip io-2022 08 19-16_46_24

Solution: Ensure that required images exist on the cluster before starting a workspace. To achieve this, we can use:

docker pull ${IMAGE}
docker save "${IMAGE}" > universal-developer-image.tar
eval $(minikube docker-env) && docker load -i  universal-developer-image.tar
  • Create a job to pull image:
kind: Job
apiVersion: batch/v1
metadata:
  name: prepull-universal-image
spec:
  template:
    metadata:
      name: prepull-universal-image
    spec:
      containers:
        - name: prepull-universal-image
          image: "${IMAGE}"
          imagePullPolicy: Always
      restartPolicy: OnFailure

Che version

next (development version)

Steps to reproduce

  1. Deploy Eclipse Che on minikube
  2. Try to start a workspace

Expected behavior

Workspace is up and running

Runtime

minikube

Screenshots

No response

Installation method

chectl/next

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
RomanNikitenkocommented, Sep 13, 2022

Another workaround is to pull image locally and copy it to minikube

docker pull ${IMAGE}
docker save "${IMAGE}" > universal-developer-image.tar
eval $(minikube docker-env) && docker load -i  universal-developer-image.tar

I guess this part can be replaced by minikube ssh "docker pull ${IMAGE}"

I had a big image and the following commands took too long time for me:

docker save “${IMAGE}” > universal-developer-image.tar eval $(minikube docker-env) && docker load -i universal-developer-image.tar

0reactions
tolushacommented, Aug 22, 2022

Yes it can be, but it is basically the same as https://github.com/eclipse/che/issues/21643#issuecomment-1220714353

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unable to start a workspace on fresh minikube/che install [v7 ...
Describe the bug I've created a local minikube cluster following the documentation, and deployed che to it using chectl.
Read more >
This computer doesn't have VT-X/AMD-v enabled. Enabling it ...
I tried the below command to resolve this issue and the minikube started normally. minikube start --no-vtx-check.
Read more >
Workspaces :: Tekton Tutorial
In minikube cluster it should show an output like: NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE standard (default) ...
Read more >
Introduction to Eclipse Che :: Eclipse Che Documentation
A multi-container workspace for each developer with the ability to replicate with a single click using Eclipse Che factories. Pre-built stacks with the...
Read more >
Run Kubernetes Using Minikube Cluster on The AWS Cloud
Step 1: Launch an AWS EC2 Instance · Step 2: SSH into your created EC2 Instance using your keypair from your local Terminal....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found