Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1633

vscode-camelk container going into CrashLoopBackOff state at the time of creating workspace on power for ApacheCamelK workspace

XMLWordPrintable

    • False
    • False
    • Undefined
    • Hide
      • create ApacheCamelK workspace (manually or automation)
      • go to <user>-codeready namespace, check pods. that is going in to CrashLoopBackOff state
      • state change history is: Running
        OOMKilled
        CrashLoopBackOff
        Running
      Show
      create ApacheCamelK workspace (manually or automation) go to <user>-codeready namespace, check pods. that is going in to CrashLoopBackOff state state change history is: Running OOMKilled CrashLoopBackOff Running

      workaround is to modify memory limit of "vscode-camelk" to "1.5GB" in devfile

      image: "registry.redhat.io/codeready-workspaces/plugin-kubernetes-rhel8:2.8"
name: vscode-camelk
memoryLimit: "1.5G"

        1. image-2021-03-03-18-36-54-512.png
          image-2021-03-03-18-36-54-512.png
          43 kB
        2. image-2021-03-04-17-18-39-987.png
          image-2021-03-04-17-18-39-987.png
          63 kB
        3. screenshot-1.png
          screenshot-1.png
          36 kB

              djoahi dipiki joahi (Inactive)
              djoahi dipiki joahi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: