`--workspace-env-file` flag doesn't work with DevPod UI Client only CLI

[timnolte]

What happened?
When adding --workspace-env-file=.env to the "Additional CLI flags" container won't start up with an error about a missing file. The startup path seems to not be the root of the project but somewhere else.

What did you expect to happen instead?
Just like when running devpod up . --workspace-env-file=.env where the .env file is in the repository root the DevPod UI startup should find the file.

How can we reproduce the bug? (as minimally and precisely as possible)

My devcontainer.json:

{
    "name": "...",
    "dockerComposeFile": "../docker-compose.yml",
    "service": "app",
    "mounts": ["source=dind-var-lib-docker,target=/var/lib/docker,type=volume"],
    "workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}",
  
    "customizations": {
      "vscode": {
        // Set *default* container specific settings.json values on container create.
        "settings": {},
  
        // Add the IDs of extensions you want installed when the container is created.
        "extensions": ["ms-azuretools.vscode-docker"]
      }
    },
  
    // Features to add to the dev container. More info: https://containers.dev/features.
    "features": {
      "./local-features/welcome-message": "latest"
    },
  
    // Use 'forwardPorts' to make a list of ports inside the container available locally.
    "forwardPorts": [8080, 8081, 8027, 3306],
  
    // Maps a port number, "host:port" value, range, or regular expression to a set of default options. See port attributes for available options
    "portsAttributes": {
      "8080": {
        "label": "WordPress Development/Testing Site"
      },
      "8081": {
        "label": "phpMyAdmin"
      },
      "8027": {
        "label": "MailHog"
      },
      "3306": {
        "label": "MariaDB"
      }
    },
  
    // Use `onCreateCommand` to run commands as part of the container creation.
    //"onCreateCommand": "sudo chmod +x .devcontainer/install.sh && .devcontainer/install.sh",
  
    // Use 'postCreateCommand' to run commands after the container is created.
    "postCreateCommand": "sudo chmod +x .devcontainer/setup.sh && .devcontainer/setup.sh",
  
    // Use 'postStartCommand' to run commands after the container has started.
    "postStartCommand": "sudo chmod +x .devcontainer/start.sh && .devcontainer/start.sh",
  
    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
    "remoteUser": "wp_php",
  
    // A set of name-value pairs that sets or overrides environment variables for the devcontainer.json supporting service / tool (or sub-processes like terminals) but not the container as a whole.
    "remoteEnv": { "LOCAL_WORKSPACE_FOLDER": "${localWorkspaceFolder}" }
}

Local Environment:

• DevPod Version: v0.6.15
• Operating System: linux
• ARCH of the OS: AMD64

DevPod Provider:

• Local/remote provider: docker

[github-actions]

This issue is stale because it has been open for 60 days with no activity.
It will be closed in 30 days on inactivity.