Description of problem:

CPU/Memory limits and requests,as set in the Devfile, are ignored for the FIRST container.

For second (and subsequent) container are respected.

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. Create workspace out of following Devfile https://github.com/agiertli/demo-web-multi-container-resources/blob/main/devfile.yaml The issue is reproducible in Dev Sandbox

Actual results:

First container is setting requests/limits as this:

  - name: tools-limit-test
    container:
      image: registry.redhat.io/devspaces/udi-rhel8@sha256:ac5aaba0bbf1caa7f23205ab837e3029ff9f605211ebf38bdf4b9f1b8fb1ba83
      memoryLimit: 1Gi
      memoryRequest: 512Mi
      cpuRequest: 200m

But it looks completely different on the cluster:

On second (and subsequent) containers, they are set correctly

  - name: second-container
    container:
      memoryRequest: 513Mi
      memoryLimit: 1Gi
      cpuRequest: 105m

See:

The CPU Limit is set to 1 on this screenshot, but this is consequence of having a LimitRange inside the Dev Sandbox, so it's not an issue here.

Expected results:

CPU/Memory limits and requests are set correctly for every container defined in Devfile

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Dev Spaces 3.4

Additional info (Such as Logs, Screenshots, etc):