devspace icon indicating copy to clipboard operation
devspace copied to clipboard

windows is not work

Open Feeeenng opened this issue 2 months ago • 1 comments

What happened?
Using devspace dev and then connecting VS Code via SSH to launch editor does not work on Windows.

What did you expect to happen instead?
“On my Windows machine, if I open VSCode and run devspace dev from the integrated terminal, then execute devspace run code, I can successfully open and access the pod.”

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

My devspace.yaml:

version: v2beta1
name: test



localRegistry:
  enabled: false


# This is a list of `pipelines` that DevSpace can execute (you can define your own)
pipelines:
  # This is the pipeline for the main command: `devspace dev` (or `devspace run-pipeline dev`)
  dev:
    run: |-
      run_dependencies --all       # 1. Deploy any projects this project needs (see "dependencies")
      ensure_pull_secrets --all    # 2. Ensure pull secrets
      create_deployments --all     # 3. Deploy Helm charts and manifests specfied as "deployments"
      start_dev app                # 4. Start dev mode "app" (see "dev" section)
      #code --folder-uri vscode-remote://ssh-remote+ssh.devspace/home/myapp
      
  # You can run this pipeline via `devspace deploy` (or `devspace run-pipeline deploy`)
  deploy:
    run: |-
      run_dependencies --all                            # 1. Deploy any projects this project needs (see "dependencies")
      ensure_pull_secrets --all                         # 2. Ensure pull secrets
      build_images --all -t $(git describe --always)    # 3. Build, tag (git commit hash) and push all images (see "images")
      create_deployments --all                          # 4. Deploy Helm charts and manifests specfied as "deployments"

# This is a list of `images` that DevSpace can build for this project
# We recommend to skip image building during development (devspace dev) as much as possible
images:
  app:
    image: backend
    dockerfile: Dockerfile
    context: .
    tags:
    - $(git describe --always)

# This is a list of `deployments` that DevSpace can create for this project
deployments:
  app:
    # This deployment uses `kubectl` but you can also define `helm` deployments
    updateImageTags: true
    kubectl:
      manifests:
        - install/kubernetes/cube/overlays
      kustomize: true

# This is a list of `dev` containers that are based on the containers created by your deployments
dev:
  app:
    # Search for the container that runs this image
    imageSelector: dashboard-enterprise:Test
    namespace: test
    # Replace the container image with this dev-optimized image (allows to skip image building during development)
    devImage: kubeflow-dashboard:base-python3.9
    # Sync files between the local filesystem and the development container
    sync:
      - path: ./myapp:/home/
        waitInitialSync: false
        disableDownload: true
        initialSync: preferRemote
        excludePaths:
          - __pycache__/
          - .git/
          - myapp/frontend/node_modules/*
      - path: ./start.sh:/home/myapp/start.sh
        file: true
      # - path: ./install/kubernetes/c````````ube/overlays/config/config.py/:/tmp/myapp-dev/
    # Open a terminal and use the following command to start it
    env:
      - name: STAGE
        value: dev
      - name: PYTHONPATH
        value: /home/myapp
    terminal:
      command: /bin/bash
    # Inject a lightweight SSH server into the container (so your IDE can connect to the remote dev env)
    ssh:
      enabled: true
      localHostname: ssh.devspace
      localPort: 2222
    # Make the following commands from my local machine available inside the dev container
    proxyCommands:
      - command: devspace
      - command: kubectl
      - command: helm
      - gitCredentials: true
    # Forward the following ports to be able access your application via localhost
    ports:
      - port: "8080:80"
      - port: "3000:3000"
    # Open the following URLs once they return an HTTP status code other than 502 or 503
    open:
      - url: http://localhost:8080
      - url: http://localhost:3000

# Use the `commands` section to define repeatable dev workflows for this project 
commands:
  enter:
      command: devspace enter
  start:
    command: |
      devspace enter -- bash -c '

        # start dev
        python run.py'
  code:
    command: |
      code --folder-uri vscode-remote://ssh-remote+ssh.devspace/home/myapp


...

Local Environment:

  • DevSpace Version: [use devspace --version] devspace version 6.3.18
  • Operating System: windows | linux | mac windows develop. liunx K8S cluster
  • ARCH of the OS: AMD64 | ARM64 | i386 Kubernetes Cluster:
  • Cloud Provider: google | aws | azure | other
  • Kubernetes Version: [use kubectl version]

Anything else we need to know?

Feeeenng avatar Dec 02 '25 10:12 Feeeenng

I use Devspace for my developers from Windows; it works fine. Did you get any errors? Does devspace dev start your pods?

dajrivera avatar Dec 05 '25 22:12 dajrivera

I use Devspace for my developers from Windows; it works fine. Did you get any errors? Does devspace dev start your pods?

I can start my pod, but after enabling SSH, I can’t SSH into the pod.

Feeeenng avatar Dec 15 '25 01:12 Feeeenng