<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=510915) </details> <!--IssueSummary end--> <!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary When specifying a second container definition in the `.devfile.yaml` file the workspace remains in the `creating` state and no pod is created. The agent log shows the following error relating to a duplicate entry for a volumeMount: ``` "ApplyEvent{ GroupName: \"apply-0\", Status: \"Failed\", Identifier: \"gl-rd-ns-3-33-kwfqnj_workspace-3-33-kwfqnj_apps_Deployment\", Error: \"failed to create typed patch object (gl-rd-ns-3-33-kwfqnj/workspace-3-33-kwfqnj; apps/v1, Kind=Deployment): .spec.template.spec.containers[name=\\\"tooling-container2\\\"].volumeMounts: duplicate entries for key [mountPath=\\\"/projects\\\"]\" }" ``` The devfile is: ``` schemaVersion: 2.2.0 variables: registry-root: registry.gitlab.com components: - name: tooling-container attributes: gl/inject-editor: true container: image: "{{registry-root}}/gitlab-org/remote-development/gitlab-remote-development-docs/ubuntu:22.04" endpoints: - name: example-app protocol: https targetPort: 8000 exposure: public - name: tooling-container2 container: image: "docker:dind" endpoints: - name: example-app2 protocol: https targetPort: 8001 exposure: public ``` The [documentation](https://docs.gitlab.com/ee/user/workspace/#:\~:text=The%20devfile%20must%20have%20at%20least%20one%20component) and [this FAQ issue](https://gitlab.com/gitlab-org/gitlab/-/issues/471911#note_2170246447) suggest it should be possible to provision service containers alongside the main editor container. Am I missing some configuration? Or is this actually not supported? Using GitLab version 17.7 and Agent version 17.7.0 ### Steps to reproduce <!--Describe how one can reproduce the issue - this is very important. Please use an ordered list.--> ### Example Project <!--If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version.--> ### What is the current *bug* behavior? <!--Describe what actually happens.--> ### What is the expected *correct* behavior? <!--Describe what you should see instead.--> ### Relevant logs and/or screenshots <!--Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.--> ### Output of checks <!--If you are reporting a bug on GitLab.com, uncomment below--> <!--This bug happens on GitLab.com--> <!--and uncomment below if you have /label privileges--> <!--/label ~"reproduced on GitLab.com"--> <!--or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not--> #### Results of GitLab environment info <!--Input any relevant GitLab environment information if needed.--> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`) </pre> </details> #### Results of GitLab application Check <!--Input any relevant GitLab application check information if needed.--> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!--If you can, link to the line of code that might be responsible for the problem.--> <!--If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"`-->